Skip to content

Update build image docs#28479

Open
yomna-shousha wants to merge 2 commits intoproductionfrom
yomna/update-build-image
Open

Update build image docs#28479
yomna-shousha wants to merge 2 commits intoproductionfrom
yomna/update-build-image

Conversation

@yomna-shousha
Copy link
Contributor

Draft

@github-actions
Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/pages/ @cloudflare/workers-docs, @GregBrimble, @WalshyDev, @aninibread, @irvinebroque, @cloudflare/pcx-technical-writing
/src/content/docs/workers/ci-cd/ @irvinebroque, @aninibread, @GregBrimble, @cloudflare/pcx-technical-writing, @yomna-shousha
* @cloudflare/pcx-technical-writing

@elithrar
Copy link
Collaborator

/bonk review this and suggest any fixes for @yomna-shousha to address.

@ask-bonk
Copy link
Contributor

ask-bonk bot commented Feb 23, 2026

Review posted. Here is a summary:


PR #20677 Review Summary

The PR replaces vague "Any version" supported-version labels with specific ceiling values ("Any version up to X.Y.Z") in the Pages build environment YAML files and updates the corresponding note in the docs. It also bumps Ruby to 3.4.7 and adds uv as a tool on the Workers build image page.

3 suggestions posted for @yomna-shousha:

  1. Note visibility (Medium) — The "Supported versions" note only appears under Languages, but the Tools table also shows "Any version up to..." entries. Consider moving the note higher so it covers both tables.
  2. uv row ordering (Low) — The new uv row could be grouped with other Python-ecosystem tools (after poetry) rather than between pipx and bundler.
  3. uv environment variable (Low) — If uv supports version pinning via an env var, it should be listed for consistency with other tools.

No build-breaking issues, MDX syntax problems, or frontmatter errors found.

github run

@yomna-shousha
Copy link
Contributor Author

Working on a release to auto-update version releases so this draft hopefully should not be needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants