Prepare RubyGems release#3
Conversation
tylergibbs1
force-pushed
the
codex/sdk-distribution-readiness
branch
from
3170bc9 to
3502dc2
Compare
tylergibbs1
force-pushed
the
codex/sdk-distribution-readiness
branch
from
3502dc2 to
c988237
Compare
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c988237af5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| pull_request: | ||
| push: | ||
| branches: | ||
| - master |
There was a problem hiding this comment.
The workflow only triggers on push to master, so commits pushed to the repository’s active main branch will not run CI at all. In this repo, that means the new syntax/build/load-path checks can be bypassed on normal branch updates, allowing regressions to land without automated validation.
Useful? React with 👍 / 👎.
1 participant
Summary
Validation
ruby -c lib/verity.rbgem build verity-sdk.gemspecRelease note
Requires a pending RubyGems Trusted Publisher for gem
verity-sdk, repobackworkai/verity-ruby, workflowrelease.yml, environmentrelease.