Skip to content

Investigate CI by pinning Bundler 4.0.8#73

Draft
scotttrinh wants to merge 3 commits intomainfrom
investigate/pin-bundler-4.0.8
Draft

Investigate CI by pinning Bundler 4.0.8#73
scotttrinh wants to merge 3 commits intomainfrom
investigate/pin-bundler-4.0.8

Conversation

@scotttrinh
Copy link
Collaborator

Goal

Pin Bundler back to 4.0.8 in the Ruby sandbox examples and leave uv unpinned to test whether the Ruby example failure tracks the Bundler upgrade.

What changed

  • pin Bundler to 4.0.8 in the Ruby sandbox examples
  • split CI into separate lint-and-tests, example-tests, and build-package jobs so the Ruby example result does not mask the build result

Expected interpretation

  • if example-tests passes and build-package still fails, that supports Bundler drift as the Ruby-side cause and an independent Python-side issue
  • if both still fail, the Bundler upgrade alone is probably not sufficient to explain the Ruby regression

Pin Bundler to 4.0.8 in the Ruby sandbox examples so we can test\nwhether the example failure tracks the Bundler upgrade.\n\nSplit CI into separate test, example, and build jobs so the Ruby\nexample result does not mask the package build outcome.
@vercel
Copy link

vercel bot commented Mar 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vercel-py Ready Ready Preview Mar 25, 2026 3:44pm

Request Review

Apply the repository formatter output for the Bundler pin\ninvestigation branch.
Revert the investigation workflow split so this branch matches the\nmain CI job structure while keeping the Bundler pin in place.
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