Skip to content

Commit 438ac8e

Browse files
authored
Merge pull request #531 from zendesk/RED-1630-autodeploy
Auto publish gem to RubyGems
2 parents c0492ef + 7f826d7 commit 438ac8e

File tree

4 files changed

+26
-7
lines changed

4 files changed

+26
-7
lines changed

.github/workflows/publish_gem.yml

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
name: Publish Gem
2+
3+
on:
4+
push:
5+
tags: v*
6+
7+
jobs:
8+
call-workflow:
9+
uses: zendesk/gw/.github/workflows/ruby-gem-publication.yml@main
10+
secrets:
11+
RUBY_GEMS_API_KEY: ${{ secrets.RUBY_GEMS_API_KEY }}
12+
RUBY_GEMS_TOTP_DEVICE: ${{ secrets.RUBY_GEMS_TOTP_DEVICE }}

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@
44

55
- Upcoming changes
66

7+
## v2.0.1
8+
9+
- More complete error message for `RecordInvalid`
10+
711
## v2.0.0 (BREAKING!)
812

913
- Add support for Faraday 2.0

README.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -431,11 +431,12 @@ bundle exec rubocop # Runs the lint (use `--fix` for autocorrect)
431431

432432
## Releasing a new gem version
433433

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
436+
3. Push to GitHub `git push && git push origin vX.X.X`
437+
4. Raise a PR and get it approved and merged
438+
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)
439440

440441
## Contributing
441442

@@ -448,8 +449,10 @@ bundle exec rubocop # Runs the lint (use `--fix` for autocorrect)
448449
we can ignore when we pull.)
449450
5. Submit a pull request.
450451

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.
453+
451454
## Copyright and license
452455

453-
Copyright 2015-2022 Zendesk
456+
Copyright 2015-2023 Zendesk
454457

455458
See [LICENSE](./LICENSE).

lib/zendesk_api/version.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
module ZendeskAPI
2-
VERSION = "2.0.0"
2+
VERSION = "2.0.1"
33
end

0 commit comments

Comments
 (0)