Repository navigation
Commit 05087f7
Update gemfile locks via sed instead of bundle lock
The rails_main and rails_main_head appraisals target ruby-head / a
future Ruby (e.g. 4.1.0.dev). Running `bundle lock` on them from the
release job's Ruby 4.0 — even with BUNDLE_IGNORE_RUBY_VERSION=1 —
produces lockfiles that CI on ruby-head then wants to rewrite, and
rejects because Bundler is running in frozen mode:
Cannot write a changed lockfile while frozen.
The running version of Bundler (4.0.16) does not match the version
of the specification installed for it (4.1.0.dev).
The only thing that actually changes in a lockfile during a release is
the view_component version pinned by the path gemspec (e.g. 4.13.0 →
4.14.0). Replace the bundle lock loop with a targeted sed that rewrites
that version in every Gemfile.lock / gemfiles/*.gemfile.lock. This is
robust across mismatched Ruby versions and avoids running bundler at
all for appraisals whose Ruby isn't installed.
Verified locally: sed rewrites both the PATH-section spec line and the
bottom DEPENDENCIES pin, matching only the view_component entry.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 217f0a0d-a9f2-4607-9643-5fcb3e34f20f1 parent 356ccc4 commit 05087f7
1 file changed
Lines changed: 16 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
64 | | - | |
65 | | - | |
66 | | - | |
67 | | - | |
68 | | - | |
69 | | - | |
70 | | - | |
71 | | - | |
72 | | - | |
73 | | - | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
74 | 80 | | |
75 | 81 | | |
76 | 82 | | |
| |||
0 commit comments