@@ -23,17 +23,17 @@ See: [RubyGems Security Guide][🔒️rubygems-security-guide]
23
23
3 . Run ` bin/setup && bin/rake ` again as a secondary check, and to update ` Gemfile.lock `
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
- a. NOTE: Remember to [ check the build] [ 🧪build ] !
26
+ - NOTE: Remember to [ check the build] [ 🧪build ] !
27
27
6 . Run ` git checkout main `
28
28
7 . Run ` git pull origin main ` to ensure you will release the latest trunk code.
29
29
8 . Set ` SOURCE_DATE_EPOCH ` so ` rake build ` and ` rake release ` use same timestamp, and generate same checksums
30
- a. Run ` export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH `
31
- b. If the echo above has no output, then it didn't work.
32
- c. Note that you'll need the ` zsh/datetime ` module, if running ` zsh ` .
33
- d. In ` bash ` you can use ` date +%s ` instead, i.e. ` export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH `
30
+ - Run ` export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH `
31
+ - If the echo above has no output, then it didn't work.
32
+ - Note that you'll need the ` zsh/datetime ` module, if running ` zsh ` .
33
+ - In ` bash ` you can use ` date +%s ` instead, i.e. ` export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH `
34
34
9 . Run ` bundle exec rake build `
35
35
10 . Run [ ` bin/checksums ` ] [ 🔒️rubygems-checksums-pr ] to create SHA-256 and SHA-512 checksums
36
- a. Checksums will be committed automatically by the script, but not pushed
36
+ - Checksums will be committed automatically by the script, but not pushed
37
37
11 . Run ` bundle exec rake release ` which will create a git tag for the version,
38
38
push git commits and tags, and push the ` .gem ` file to [ rubygems.org] [ 💎rubygems ]
39
39
0 commit comments