Bump Ruby to 4.0.6 and Playwright to 1.61.1 - #1
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the CI base image to match downstream consumer requirements by bumping the pinned Ruby patch version and keeping the baked Playwright browser install aligned with the Playwright version resolved by consumers (avoiding repeated browser downloads during CI jobs).
Changes:
- Bump Docker base image from
rubylang/ruby:4.0.5-dev-nobletorubylang/ruby:4.0.6-dev-noble. - Bump baked Playwright install from
playwright@1.60.0toplaywright@1.61.1for Chromium.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Ruby 4.0.5 → 4.0.6
pulsify-core bumped to Ruby 4.0.6 (
mise.toml), and itsGemfileusesruby file: "mise.toml", which bundler turns into an exact versionrequirement. Every job on that repo's CI is currently failing at
bundle install:The weekly cron rebuild can't fix this on its own —
FROMis pinned to apatch tag, so it rebuilds 4.0.5 indefinitely.
Playwright 1.60.0 → 1.61.1
The Dockerfile comment asks that the baked browser stay in sync with the
version consumers resolve to. pulsify-core's lockfile now resolves
playwright@1.61.1, so itsnpx playwright install chromiumstep hasbeen re-downloading chromium on every run instead of being the intended
no-op.