|
2 | 2 |
|
3 | 3 | ## Automatic |
4 | 4 |
|
5 | | -1. Create PR with following changes: |
6 | | - 1. Update version in `gradle.properties`. |
7 | | - 2. Create a new section with version name taking all changes from pending section. |
8 | | -2. Create GitHub release with a tag name of the version and fill notes from pending changes section. |
9 | | -3. Library is published to staging repository automatically with GitHub Action. |
10 | | -4. Proceed to 'Closing staging repository'. |
| 5 | +1. Create a PR with the following changes: |
| 6 | + 1. Update the version in `gradle.properties`. |
| 7 | + 2. Create a new section with the version name, including all changes from the pending section. |
| 8 | +2. Create a GitHub release with a tag name matching the version and fill in the release notes using the pending changes section. |
| 9 | +3. The library will be published to the staging repository automatically via GitHub Actions. |
| 10 | +4. [Proceed to closing the staging repository](#closing-staging-repository). |
11 | 11 |
|
12 | | -In case of any issues you can launch Release manually from GitHub Actions tab. |
| 12 | +If any issues arise, you can manually launch the release from the GitHub Actions tab. |
13 | 13 |
|
14 | 14 | ## Manual |
15 | 15 |
|
16 | | -Should be used in case if there are issues with automatic publication. |
17 | | - |
18 | | -1. Create PR with following changes: |
19 | | - 1. Update version in `gradle.properties`. |
20 | | - 2. Create a new section with version name taking all changes from pending section. |
21 | | -2. `./gradle publishAppyxReleasePublicationToOSSRHRepository --no-parallel -Psigning.keyId=$KEY_ID -Psigning.password=$PASS -Psigning.secretKeyRingFile=$FILE -Psonatype.username=$NAME -Psonatype.password=$PASS` |
22 | | - 1. `signing` properties are related to signing information. |
23 | | - 2. `sonatype` properties are your username and password from `oss.sonatype.org`. |
24 | | - 3. `--no-parallel` is required to avoid creation of multiple staging repositories. |
25 | | -3. Create GitHub release with a tag name of the version and fill notes from pending changes section. |
26 | | -4. Cancel Release GitHub Action as it will fail now because version is already released. |
27 | | -5. Proceed to 'Closing staging repository'. |
28 | | - |
29 | | -## Closing staging repository |
30 | | - |
31 | | -1. Open `https://s01.oss.sonatype.org` and sign in with the sonatype credentials. |
32 | | -2. Click `Staging Repositories`. |
33 | | -3. Select the repository (assuming publish succeeded) and click the close button. |
34 | | -4. Select the repository again and click release. |
| 16 | +This process should be used if there are issues with automatic publication. |
| 17 | + |
| 18 | +1. Create a PR with the following changes: |
| 19 | + 1. Update the version in `gradle.properties`. |
| 20 | + 2. Create a new section with the version name, including all changes from the pending section. |
| 21 | +2. Refer to [.github/workflows/release.yml](.github/workflows/release.yml) for the manual release process. |
| 22 | + - Check the [vanniktech.github.io plugin documentation](https://vanniktech.github.io/gradle-maven-publish-plugin/central/#secrets) to learn how to use Gradle properties instead of environment variables. |
| 23 | +3. Create a GitHub release with the version's tag name and fill in the release notes using the pending changes section. |
| 24 | +4. Cancel the `Release` GitHub Action, as it will fail because the version has already been released. |
| 25 | +5. [Proceed to closing the staging repository](#closing-staging-repository). |
| 26 | + |
| 27 | +## Closing the Staging Repository |
| 28 | + |
| 29 | +1. Open [Sonatype Central](https://central.sonatype.com/publishing) and sign in with the Sonatype credentials. |
| 30 | +2. Click `Deployments` and then `Publish` once validated. |
| 31 | + |
| 32 | +For more information, refer to [the official documentation](https://central.sonatype.org/publish/publish-portal-guide/#component-validation). |
0 commit comments