Skip to content

Add release workflow for automated gem publishing#15

Merged
cpetersen merged 4 commits intomainfrom
add-release-workflow
Mar 24, 2026
Merged

Add release workflow for automated gem publishing#15
cpetersen merged 4 commits intomainfrom
add-release-workflow

Conversation

@cpetersen
Copy link
Copy Markdown
Member

Triggers on semver tags, verifies version matches, builds gem, pushes to RubyGems, creates GitHub Release. Requires RUBYGEMS_API_KEY secret (already set as org secret).

cpetersen and others added 4 commits March 23, 2026 13:59
rb-sys 0.9.117 did not support Ruby 4.0's C API changes, causing
"Failed to setup stable API" during native extension compilation.

- Update magnus from 0.6 to 0.8 in Cargo.toml
- Update rb-sys from 0.9.117 to 0.9.124 in Cargo.lock
- Migrate all Rust source files from deprecated magnus 0.6 APIs to
  the new Ruby-handle-based 0.8 APIs (Ruby::get().unwrap() pattern)
- Zero deprecation warnings

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replaces tag-triggered release with workflow_dispatch so releases
can be initiated from the GitHub Actions UI with a version input.
The workflow updates version.rb, commits, tags, builds, and publishes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@cpetersen cpetersen force-pushed the add-release-workflow branch from 7c57e81 to cc9ffd4 Compare March 24, 2026 00:52
@cpetersen cpetersen merged commit 3bc886a into main Mar 24, 2026
1 check passed
@cpetersen cpetersen deleted the add-release-workflow branch March 24, 2026 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant