Skip to content

Bump Ruby to 4.0.6 and Playwright to 1.61.1 - #1

Merged
hakanensari merged 1 commit into
mainfrom
bump-ruby-4.0.6-playwright-1.61.1
Aug 20, 2026
Merged

Bump Ruby to 4.0.6 and Playwright to 1.61.1#1
hakanensari merged 1 commit into
mainfrom
bump-ruby-4.0.6-playwright-1.61.1

Conversation

@hakanensari

Copy link
Copy Markdown
Member

Ruby 4.0.5 → 4.0.6

pulsify-core bumped to Ruby 4.0.6 (mise.toml), and its Gemfile uses
ruby file: "mise.toml", which bundler turns into an exact version
requirement. Every job on that repo's CI is currently failing at
bundle install:

Your Ruby version is 4.0.5, but your Gemfile specified 4.0.6
##[error]Process completed with exit code 18

The weekly cron rebuild can't fix this on its own — FROM is pinned to a
patch 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 its npx playwright install chromium step has
been re-downloading chromium on every run instead of being the intended
no-op.

Copilot AI lite review requested due to automatic review settings August 20, 2026 19:48

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-noble to rubylang/ruby:4.0.6-dev-noble.
  • Bump baked Playwright install from playwright@1.60.0 to playwright@1.61.1 for Chromium.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@hakanensari
hakanensari merged commit 1ea5fb5 into main Aug 20, 2026
1 check 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.

3 participants