Skip to content

Commit 91bfc0e

Browse files
committed
Update RELEASING.md: GitHub Actions, MFA/OTP instructions.
1 parent ec3a353 commit 91bfc0e

1 file changed

Lines changed: 14 additions & 5 deletions

File tree

RELEASING.md

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ bundle install
1111
rake
1212
```
1313

14-
Check that the last build succeeded in [Travis CI](https://travis-ci.org/dblock/ruby-enum) for all supported platforms.
14+
Check that the last build succeeded in [GitHub Actions](https://github.com/dblock/ruby-enum/actions) for all supported platforms.
1515

1616
Add a date to this release in [CHANGELOG.md](CHANGELOG.md).
1717

@@ -28,15 +28,24 @@ git add README.md CHANGELOG.md lib/ruby-enum/version.rb
2828
git commit -m "Preparing for release, 0.2.2."
2929
```
3030

31-
Release.
31+
Release. If you have MFA enabled on RubyGems (you should), `rake release` will build the gem, tag it, and push commits/tags to GitHub, but fail at the RubyGems push. Push the gem manually with your OTP.
3232

3333
```
3434
$ rake release
3535
36-
ruby-enum 0.2.2 built to pkg/ruby-enum-0.2.2.gem.
37-
Tagged v0.2.2.
36+
ruby-enum 1.1.0 built to pkg/ruby-enum-1.1.0.gem.
37+
Tagged v1.1.0.
3838
Pushed git commits and tags.
39-
Pushed ruby-enum 0.2.2 to rubygems.org.
39+
...
40+
You have enabled multi-factor authentication. Please enter OTP code.
41+
```
42+
43+
Then push to RubyGems manually:
44+
45+
```
46+
$ gem push pkg/ruby-enum-1.1.0.gem --otp <OTP>
47+
Pushing gem to https://rubygems.org...
48+
Successfully registered gem: ruby-enum (1.1.0)
4049
```
4150

4251
### Prepare for the Next Version

0 commit comments

Comments
 (0)