More detailed "Releasing information" #402

Activity

1. cognifloyd commented on Feb 15, 2024

   

   cognifloyd

   on Feb 15, 2024

   Last edited by cognifloyd

   Member

   More actions

   Here's what I did for the most recent release:

   I created a github release, and told github to create the tag when publishing the release.

   Then prepare the keyring in a format helm can handle:

   # get the dsa3072 gpg key from 1password (helm does not support ed25519 keys)
   gpg --import private.gpg
   # export the key into a gpg v1 keyring because helm does not support the gpg v2 format
   gpg --export-secret-key "info@stackstorm.com" > ~/.gnupg/st2-secring.gpg
   

   Then, in your clone of the stackstorm-k8s repo, on the master branch (where the latest commit should be the commit you just released/tagged):

   helm package -d index --sign . --key "info@stackstorm.com" --keyring ~/.gnupg/st2-secring.gpg
   git checkout gh-pages
   mv index/* ./
   rmdir index
   # remove the 3rd party charts so that helm doesn't try to include them in the index
   rm -r charts/
   helm repo index . --merge=index.yaml
   

   For some irritating reason I haven't figured out, helm changes the timestamps on all entries in the index. So, I only commit the newest entry for the helm package I just created, and the overall index timestamp at the end of the file.

   git add stackstorm-ha-1.0.0.tgz{,.prov}
   git add --patch index.yaml
   git commit -m 'release v1.0.0'
   # get rid of all the unnecessary timestamp changes
   git checkout -- index.yaml
   git push
   
2. cognifloyd

   added

   enhancementNew feature or requestNew feature or request

   help wantedExtra attention is neededExtra attention is needed

   documentation

   on Apr 11, 2024