Release gem on GitHub #712
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #692
This should help release the gem on GitHub. When release, you can dispatch the release workflow on GitHub Actions. Choose "Release" workflow, and run it. The workflow will:
rpush/version.rb
.v<version>
. e.g.,v9.2.0
.Because the release workflow uses an action called
rubygems/release-gem
, to publish the gem via GitHub, the gem owners must configure the "Trusted publishing". You must add GitHub as a trusted platform.Other changes:
pg
,mysql2
to resolve a few build problems on my development environment.tests.yml
to run the latest Ubuntu. This can be further improved to use GitHub repo's ruleset to set certain or all tests must pass for PR to be able to merge. Happy to help on this area too.