Add note to releasing doc about making a git tag (#130)

* Add note to releasing doc about making a git tag * Remove dead integration test info now lives in TSP * Update RELEASING.md
IronCoreLabs · Oct 25, 2023 · 778c84d · 778c84d
1 parent 7f93763
commit 778c84d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/RELEASING.md b/RELEASING.md
@@ -5,7 +5,7 @@ We deploy the SDK to [Maven Central](https://search.maven.org/artifact/com.ironc
 - Update the `<version>` in [pom.xml](./pom.xml).
 - Update the `sdkVersion` in [TenantSecurityRequest.java](./src/main/java/com/ironcorelabs/tenantsecurity/kms/v1/TenantSecurityRequest.java) to match the pom.xml.
 - Add an entry to [CHANGELOG.md](./CHANGELOG.md).
-- Commit the changes to the `main` branch. Wait until the release has succeeded to push the changes.
+- 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.
 - Put the username and password for the `icl-devops` Sonatype account into your `.m2/settings.xml` file. These credentials are stored on Drive in `IT_Info/sonatype-info.txt.iron`. A sample of this file is given below.
 - 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:
   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.
@@ -22,7 +22,7 @@ We deploy the SDK to [Maven Central](https://search.maven.org/artifact/com.ironc
     release process complete successfully.
 - When the artifacts have been deployed, go to https://oss.sonatype.org, log in using the `icl-devops` username and
   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.
-- Push your new version and CHANGELOG entry to GitHub.
+- Push your new version and CHANGELOG entry to GitHub. Create a release in github and label it as latest if it isn't already.
 
 ### Sample .m2/settings.xml
 

diff --git a/test-suites/integrationTestLogins.txt.iron b/test-suites/integrationTestLogins.txt.iron