@@ -24,17 +24,18 @@ See: [RubyGems Security Guide][🔒️rubygems-security-guide]
24
24
4 . Run ` git commit -am "🔖 Prepare release v<VERSION>" ` to commit the changes
25
25
5 . Run ` git push ` to trigger the final CI pipeline before release, & merge PRs
26
26
- NOTE: Remember to [ check the build] [ 🧪build ] !
27
- 6 . Run ` git checkout main `
28
- 7 . Run ` git pull origin main ` to ensure you will release the latest trunk code.
29
- 8 . Set ` SOURCE_DATE_EPOCH ` so ` rake build ` and ` rake release ` use same timestamp, and generate same checksums
27
+ 6 . Run ` export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME `
28
+ 7 . Run ` git checkout $GIT_TRUNK_BRANCH_NAME `
29
+ 8 . Run ` git pull origin $GIT_TRUNK_BRANCH_NAME ` to ensure you will release the latest trunk code
30
+ 9 . Set ` SOURCE_DATE_EPOCH ` so ` rake build ` and ` rake release ` use same timestamp, and generate same checksums
30
31
- Run ` export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH `
31
32
- If the echo above has no output, then it didn't work.
32
33
- Note that you'll need the ` zsh/datetime ` module, if running ` zsh ` .
33
34
- In ` bash ` you can use ` date +%s ` instead, i.e. ` export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH `
34
- 9 . Run ` bundle exec rake build `
35
- 10 . Run [ ` bin/checksums ` ] [ 🔒️rubygems-checksums-pr ] to create SHA-256 and SHA-512 checksums
35
+ 10 . Run ` bundle exec rake build `
36
+ 11 . Run [ ` bin/checksums ` ] [ 🔒️rubygems-checksums-pr ] to create SHA-256 and SHA-512 checksums
36
37
- Checksums will be committed automatically by the script, but not pushed
37
- 11 . Run ` bundle exec rake release ` which will create a git tag for the version,
38
+ 12 . Run ` bundle exec rake release ` which will create a git tag for the version,
38
39
push git commits and tags, and push the ` .gem ` file to [ rubygems.org] [ 💎rubygems ]
39
40
40
41
## Contributors
0 commit comments