Skip to content

Refresh the lockfile during the version bump - #19

Merged
springwq merged 1 commit into
mainfrom
codex/fix-bump-lockfile
Aug 22, 2026
Merged

Refresh the lockfile during the version bump#19
springwq merged 1 commit into
mainfrom
codex/fix-bump-lockfile

Conversation

@springwq

Copy link
Copy Markdown
Collaborator

The first auto-versioned publish run failed at `ruby/setup-ruby` in all four build jobs: the bump commit updated `version.rb` (0.1.1) but not `Gemfile.lock`, which records the path gem version (0.1.0) — frozen bundle installs reject the mismatch.

Changes

  • The bump job now runs `bundle lock` and commits `Gemfile.lock` together with `version.rb`.
  • This PR also repairs the current main: the stray `fm 0.1.1` bump commit is already there, so this branch carries the matching lockfile update.
  • Tests that hardcoded `0.1.0` now derive from `FeedMob::CLI::VERSION` — with auto-bump the constant changes every release.

No tag or release exists for 0.1.1, so after merging, re-running the publish command recomputes 0.1.1 and the bump job is a no-op (idempotent).

The lockfile records the path gem version, so a version.rb-only bump
left main in a state where frozen bundle installs fail. The bump job
now runs bundle lock and commits Gemfile.lock alongside version.rb.
Tests that hardcoded 0.1.0 now derive from FeedMob::CLI::VERSION so
auto-bumped versions don't break them.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@springwq
springwq merged commit adb96b9 into main Aug 22, 2026
7 checks passed
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