You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -431,11 +431,12 @@ bundle exec rubocop # Runs the lint (use `--fix` for autocorrect)
431
431
432
432
## Releasing a new gem version
433
433
434
-
1. Execute `bundle exec rake bump:minor`, which bumps the version in my local machine in a specific commit
435
-
2. Change the CHANGELOG and amend that previous commit, so the bump commit and the CHANGELOG changes are in the same commit (example)
436
-
3. Push to Github
437
-
4. Post a message in Slack `#rest-api`, so advocacy are aware that we are going to release a new gem, just in case any customer complains about something related to the gem
438
-
5. After a couple of hours, run `bundle exec rake release`, which automatically pushes the tag to GitHub and releases a new version to Rubygems (it does the gem push for you)
434
+
1. Ensure the CHANGELOG is correct and updated, this is your last opportunity
435
+
2. Execute `bundle exec bump patch --tag`, or minor or major according to [SemVer](https://semver.org), this bumps the version in your local machine in the latest commit
5. Post a message in Slack `#rest-api`, so advocacy are aware that we are going to release a new gem, just in case any customer complains about something related to the gem
439
+
6. After 2 hours from the above message, you can [approve the release of the gem](https://github.com/zendesk/zendesk_api_client_rb/deployments/activity_log?environment=rubygems-publish)
439
440
440
441
## Contributing
441
442
@@ -448,8 +449,10 @@ bundle exec rubocop # Runs the lint (use `--fix` for autocorrect)
448
449
we can ignore when we pull.)
449
450
5. Submit a pull request.
450
451
452
+
**Note:** Live specs will likely fail for external contributors. The Zendesk devs can help with that. If you have permissions and some live specs unexpectedly fail, that might be a data error, see the REPL for that.
0 commit comments