Skip to content

ci: prepare master-to-v12 docs branch rename - #1464

Merged
fhammerschmidt merged 1 commit into
masterfrom
chore/prepare-v12-branch-rename
Oct 21, 2026
Merged

fhammerschmidt merged 1 commit into
masterfrom
chore/prepare-v12-branch-rename

Conversation

@fhammerschmidt

@fhammerschmidt fhammerschmidt commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Renaming the website's default branch from master to v12 currently stops push deployments and leaves production routing and Lighthouse baselines tied to the old name.

Use the repository's default branch for docs and guide production routing, pass that branch into Lighthouse artifact selection, and accept pushes to both master and v12 during the transition. Existing production behavior and isolated manual previews continue to work before the rename.


After merging:

  1. Rename the GitHub default branch master to v12, keeping v12 as the default.
  2. Set the Cloudflare Pages project's production_branch to v12, update any deployment hooks that target master, and run a production deployment.

Before any later default-branch switch, the compiler's maintenance/12.x publication workflow must explicitly target website v12. The compiler v13 follow-up targets v13 through rescript-lang/rescript#8753.

This PR prepares the rename; it does not rename branches or change Cloudflare settings.

Derive production deployment routing and Lighthouse baseline environments from the repository default branch. Accept pushes to both master and v12 so deployment works across the rename, and cover production and manual preview behavior before and after it.

Signed-off-by: Florian Hammerschmidt <florianh89@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

Docs preview

@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse baseline

Compared with target branch master at commit 1f47ac6. Scores are the median of 3 runs against the deployed Cloudflare preview.

Category Target Current Change
Performance 85 85 0
Accessibility 80 80 0
Best practices 100 100 0
SEO 100 66 -34

Download the full Lighthouse reports and baseline

Commit 440e0ad · Cloudflare preview

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-21T15:36:18.725231Z fd635af PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
guide fd635af Commit Preview URL

Branch Preview URL
Oct 21 2026, 03:41 PM

@fhammerschmidt
fhammerschmidt merged commit e857925 into master Oct 21, 2026
11 checks passed
@fhammerschmidt
fhammerschmidt deleted the chore/prepare-v12-branch-rename branch October 21, 2026 15:41

This branch was successfully deployed

2 active deployments
preview — fd635afb Deployed Oct 21, 2026 by github-actions[bot]
guide-preview — fd635afb Deployed Oct 21, 2026 by github-actions[bot]
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.

2 participants