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: RELEASING.md
+2-4Lines changed: 2 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ We deploy the SDK to [Maven Central](https://search.maven.org/artifact/com.ironc
6
6
- Update the `sdkVersion` in [TenantSecurityRequest.java](./src/main/java/com/ironcorelabs/tenantsecurity/kms/v1/TenantSecurityRequest.java) to match the pom.xml.
7
7
- Add an entry to [CHANGELOG.md](./CHANGELOG.md).
8
8
- Commit the changes to the `main` branch and add a git tag with the `version` in it. Wait until the release has succeeded to push the changes.
9
-
- Login to https://oss.sonatype.org with the username `icl-devops` and the password which is stored in `IT_Info/sonatype-info.txt.iron`.
9
+
- Login to https://central.sonatype.org/ with the username `icl-devops` and the password which is stored in `IT_Info/sonatype-info.txt.iron`.
10
10
- In the corner with the username click the down arrow and go to profile. Then click the `Access User Token` button. Copy the username and password into your `.m2/settings.xml`. A sample of this file is given below.
11
11
- Import the GPG signing key needed to sign the release. In Google Drive, navigate to the `IT_Info/pgp` folder, download `rsa-signing-subkey.asc.iron` and `ops-info.txt.iron`, and decrypt them using IronHide. Then do the following:
12
12
1. Copy the master password from `ops-info.txt` to your clipboard so it can be provided in step 3 when importing the secret key.
@@ -21,8 +21,6 @@ We deploy the SDK to [Maven Central](https://search.maven.org/artifact/com.ironc
21
21
- To test the release process or to install `tenant-security-client-java` to your local machine, you can instead run
22
22
`mvn clean generate-resources source:jar javadoc:jar install -Dsuite=test-suites/test-unit` and verify that all steps of the
23
23
release process complete successfully.
24
-
- When the artifacts have been deployed, go to https://oss.sonatype.org, log in using the `icl-devops` username and
25
-
password from `sonatype-info.txt`, and find the new release in the _Staging Repositories_. Close that repository and then release it in order to actually push the package out to the public repo.
26
24
- Push your new version and CHANGELOG entry to GitHub. Create a release in github and label it as latest if it isn't already.
27
25
28
26
### Sample .m2/settings.xml
@@ -33,7 +31,7 @@ We deploy the SDK to [Maven Central](https://search.maven.org/artifact/com.ironc
0 commit comments