You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/releasing.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,6 @@
2
2
3
3
The H3-Java library is published to Maven Central via OSSRH.
4
4
5
-
The release is triggered via GitHub Actions, when a tag of the form `v1.2.3` is pushed, or via workflow dispatch. The release workflow handles all parts of the release.
6
-
7
-
## Old instructions for manual releasing
8
-
9
5
You must be a member of the `com.uber` group to release the library via OSSRH. You must have a [signing key](http://central.sonatype.org/pages/working-with-pgp-signatures.html) setup, and you must have your OSSRH username and password in the appropriate [Maven settings file](http://central.sonatype.org/pages/apache-maven.html).
10
6
11
7
Release builds pull artifacts from Github Actions. This is needed so that the deployed artifact contains all supported operating system/architecture combinations. (In particular, Mac OS artifacts must be built natively.) In order to release, there must be a completed build of the Git commit to release on Github. The build must be less than 30 days old, as artifacts are only kept for that time.
@@ -17,14 +13,14 @@ Release builds pull artifacts from Github Actions. This is needed so that the de
17
13
5. If this looks good, close and release the build in [Sonatype Nexus Manager](https://oss.sonatype.org/).
18
14
6. Update `CHANGELOG.md` to have an Unreleased section, and commit. The release is now done and development can resume from this point.
19
15
20
-
###Troubleshooting
16
+
## Troubleshooting
21
17
22
-
####Dependencies for `pull-from-github.sh`
18
+
### Dependencies for `pull-from-github.sh`
23
19
24
20
* You should install the [Github CLI](https://cli.github.com) and authenticate with it first. You may need to use a personal access token (classic) with workflows scope.
25
21
*`jq`
26
22
27
-
####gpg: signing failed: Inappropriate ioctl for device
23
+
### gpg: signing failed: Inappropriate ioctl for device
28
24
29
25
Per [StackOverflow](https://stackoverflow.com/questions/57591432/gpg-signing-failed-inappropriate-ioctl-for-device-on-macos-with-maven), run the following before `mvn release:perform`:
0 commit comments