Repository navigation
Prepare 0.1.0 - #7
Merged
Merged
Conversation
Bump the version to 0.1.0 and consolidate the per-phase changelog entries into one organized 0.1.0 section with known limitations and compare links. Switch the release workflow to the pattern documented by rubygems/release-gem: run it manually from main, run the tests, and let `rake release` build, tag, and publish with trusted publishing, so the tag always matches the gem version. Update RELEASING.md to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L5SuBiSMN4r9qr5CXbKkHV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prepares the first functional release,
0.1.0. Merging this does not publish anything. Publishing happens when the Release workflow is run by hand.Changes
0.1.0. A0.xrelease leaves room for API changes after real-world use before committing to 1.0.0.1.0section, grouped by area, with known limitations and compare links. It's dated 2026-10-15; adjust the date if the release happens later.rubygems/release-gem. It's started manually frommain, runs the tests, andrake releasebuilds the gem, creates and pushes thev0.1.0tag, and publishes with trusted publishing. The tag always matches the gem version, and the job refuses to run from other branches.RELEASING.mdis updated to match.Already done
rubygemsGitHub environment exists, limited to protected branches, so onlymaincan publish.Still needed before running the workflow
smswiregem, then Trusted publishers, with repositorytimimsms/smswire, workflowrelease.yml, and environmentrubygems.Verification
gem buildproducessmswire-0.1.0.gem.🤖 Generated with Claude Code
https://claude.ai/code/session_01L5SuBiSMN4r9qr5CXbKkHV