Skip to content

Update Gemfile.lock for in-range minor bumps (sqlite3, mustermann, tilt) - #3679

Merged
wadealcorn merged 1 commit into
masterfrom
lockfile-inrange-minors
Oct 16, 2026
Merged

wadealcorn merged 1 commit into
masterfrom
lockfile-inrange-minors

Conversation

@wadealcorn

Copy link
Copy Markdown
Collaborator

What

Lockfile-only update picking up in-range minor/patch bumps that the current Gemfile constraints already allow (bundle update sqlite3 sinatra qr4r):

Gem From To Note
sqlite3 2.9.6 2.10.0 direct dep (~> 2.9)
mustermann 3.0.4 3.1.1 sinatra dependency
tilt 2.6.1 2.9.0 sinatra dependency

mustermann 3.1.1 no longer depends on ruby2_keywords, so it is dropped from the lock. sinatra and qr4r were already at their latest in-range versions, so only their resolution tree moved.

No Gemfile changes — Gemfile.lock only.

Verification

  • Full RSpec suite passes (0 failures).
  • Server boots; REST API login, /api/modules, and a parametrized route (/api/modules/1) all respond correctly — confirming sinatra routing via mustermann 3.1.1 / tilt 2.9.0 is intact.

bundle update sqlite3 sinatra qr4r, picking up in-range updates that
the existing Gemfile constraints already allow:

  sqlite3    2.9.6 -> 2.10.0
  mustermann 3.0.4 -> 3.1.1   (sinatra dependency)
  tilt       2.6.1 -> 2.9.0   (sinatra dependency)

mustermann 3.1.1 no longer depends on ruby2_keywords, so it is dropped
from the lock. No Gemfile changes; lockfile only.
@wadealcorn
wadealcorn merged commit 67477c7 into master Oct 16, 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