Run bundle update #24
Loading…
Reference in a new issue
No description provided.
Delete branch "armin-bot/impress:claude/bundle-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Builds on #23 (now merged); rebased onto main.
Updates gems as far as the Gemfile's constraints allow: 40 version changes, plus
bakeadded (via async-service), withemail_validatorandmappingdropped. The Gemfile itself doesn't change, so pinned gems stay on their current major/minor: falcon (~> 0.48.0), async-http (~> 0.89.0), devise 4, sentry 5 and rack-mini-profiler 4.What moves
The async server stack under falcon 0.48.6:
Falcon's 0.x constraints allow all of these. This is the riskiest part for production.
Auth: openid_connect 2.3.1 → 2.5.0, json-jwt 1.17.2, faraday 2.15.1, bcrypt 3.1.22, hashie 5.2.0.
Assets and views: sprockets 4.2.2 → 4.4.1, haml 7.2 → 7.5.1, terser 1.2.8, turbo-rails 2.0.23.
bindata 2 → 3 (via json-jwt).
Supply-chain cooldown
No gem here is younger than 14 days. Newer releases are held back to their newest older version, for example:
The one exception is sanitize 7.0.2 from #23, because it's a security fix.
Other
vendor/cachehas every platform's gems (bundle cache --all-platforms), sobundle install --localstill works on aarch64-linux and arm64-darwin. An earlier draft had dropped those, and review caught it..bundler-audit.yml: removes the bcrypt entry, since 3.1.22 fixes GHSA-f27w-vcwj-c954.Testing
bundle exec rspecpasses: 422 examples, including the HTTP/2 connection pool regression spec from #22.bin/rails testpasses.bin/security-scan --osvis clear, with no stale ignores.falcon hostboots 2 workers, serves pages, respawns a killed worker, and shuts down cleanly on SIGTERM.bin/neopass-server.assets:precompilesucceeds with the deploy job's environment.AuthHashbehaves the same, that bindata 3 works with json-jwt (RS256/JWE), and thatAsync::HTTP::Internetworks against a local server.Worth watching after deploy: the async stack. The intermittent HTTP/2 pool bug from #22 only showed up under production load.
Not included
These are majors, or blocked by Gemfile pins. They're for a separate pass if you want them:
🤖 Generated with Claude Code
https://claude.ai/code/session_014PWWd1Ljyt9gAxzYFpJgJx
b27fa4de5fa3239db87d