From 778c84ddbb938827f24631f192672dcd8fe697f1 Mon Sep 17 00:00:00 2001 From: Murph Murphy Date: Wed, 25 Oct 2023 11:46:29 -0600 Subject: [PATCH] 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 --- RELEASING.md | 4 ++-- test-suites/integrationTestLogins.txt.iron | Bin 897 -> 0 bytes 2 files changed, 2 insertions(+), 2 deletions(-) delete mode 100644 test-suites/integrationTestLogins.txt.iron diff --git a/RELEASING.md b/RELEASING.md index f078200..88a43cc 100644 --- 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 `` 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 deleted file mode 100644 index cc5a83b9f75e99177d97529f7afbaea8ca046970..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 897 zcmV-{1AhDh06BXiUu0=yUm`jpIX5?EIXGrCWn*DDH!@>kH#RmfVq{}tI5s(DVK6jg zA}k_bb7^E>B04cPI5K@MqBNkl)8*&>N0uDGZ+2c$c|deq!|@JVVs;S&az?D`6KdI$ z=1CXD90Kb>o)EWp)Z&9KEu>0Wh#4CZm*KJ~{eMB#>CMOu@>ZB9fhM6j{P4BK1;y65 z=6*wbbWTel9g?$W2ytcTTvts$2>1rt0E+#(b43zLQfQIelKqJ)%v)?Y{q4uo>X2*p z%M+=gC61-e1!aDhnu{AqG3G7g@IZCUDR}x2G<&fUh?NWM?nUKThvPlFv2w8}B)aZ& z{DS=^Bo{XtDHH4Gd53=L&pw-^;y%{9Sf+qEcAhJu%G<j3g2rBE8(_7i4I#1Yor;0H;7i(6U=YAQhGCE+wD?I`PBC-O5m{(~?;``FNB`JD zmWQ=LwzovPNKLZ$t{R=>;k8&ws_MaoXfMGocG^S)^)ve!n;ay)ix%l}YDC=c9TliH_8-?IshjwvgE z>O}NfE4DVmD|)^1ke7Na;0J1pEOO`rgWd@y@cOvv3xwmrwD4j%lE)iFV0A<=Ug$QJ zr5Ar7WoWurO@|f9R>wFj{{g~CQBrd#4HmS1=%pzc#vqso>4}TBAVWl@3=!F$CYDR0 z_6<(`j*;*tf#lwtpm0hNS3`VqAX=yXE^UugDsuUieeY#GOP= X{87O;qu*?$4(^!oh98cl1le_4HMp`J