Repository navigation
ci(pages): publish Stable and Next from one composed Pages tree - #863
Merged
Merged
Conversation
Exoridus
enabled auto-merge (squash)
October 22, 2026 11:49
Bundle ReportChanges will decrease total bundle size by 6.5kB (-0.02%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: exo-full-iife-min-Exo-iifeAssets Changed:
view changes for bundle: exo-esm-esmAssets Changed:
view changes for bundle: site-server-esmAssets Changed:
view changes for bundle: exo-iife-min-Exo-iifeAssets Changed:
|
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.
Activates the combined Stable/Next Pages publisher on the default branch.
workflow_runworkflows run from the default branch, so the publisher that already lives onnexthas never been able to run;mainstill carried the old single-channel deploy. This PR brings only the publisher infrastructure tomain— no engine, site or package source fromnext.After it lands, every successful CI push run on
mainornextwakes the publisher, which re-decides both channels from GitHub metadata and deploys one tree: Stable athttps://exoridus.github.io/ExoJS/, Next athttps://exoridus.github.io/ExoJS/next/.Changes
scripts/pages/*and their tests (test/site/pages-*.test.ts,test/support/archive-fixtures.ts): the selection, verification and composition scripts, identical tonext. The publisher runs them from a sparse checkout of the default branch, never from a candidate..github/workflows/deploy-pages.yml: the publisher, identical tonext..github/workflows/ci.yml,sitejob: the built tree is now recorded and verified as a Stable candidate and uploaded assite-stable-<sha>-<attempt>(90 days for a push); the smoke job downloads exactly that candidate.scripts/pages/stamp-stable-site.ts(main only): this branch's site build has a fixed/ExoJS/base and writes nosite-build.json, so CI records the finished tree's identity and content after the build. It refuses a tree that already has a manifest, has noindex.html, or does not reference the Stable base. A channel-aware site build (as onnext) makes it unnecessary oncenextis released tomain.test/ci/pages-deployment.test.ts: the publisher contract fromnext, with theci.ymlpart adapted to the stamp step.release.ymlis unchanged; itssite-dist-<sha>upload is no longer a publisher input, so Stable comes from the CI push.Bootstrap
There is no earlier
channels.jsonsnapshot, so the first run needs a qualified candidate for both channels. The merge commit's CI push run produces the Stable candidate; Next comes from the newest successfulnextpush run, which already uploadssite-next-<sha>-<attempt>. Neither PR builds nor fork artifacts qualify.Stable preservation
The live Stable site was deployed from
1eb0afefb(0.19.1).mainhas since moved by two dependency bumps only. A local build of this branch, compared with the live site:_astro/*bundles (new content hashes, inline loader minification), the Pagefind index, and theBuildInforevision in the vendored engine.Validation
test/site/pages-*.test.ts,test/ci), typecheck gates.site:build,stamp-stable-site,channel-artifact verify --channel stable: 13 539 files, 402 MB.faa9c61a7(314 MB): no problems, no cross-channel references, 721 MB composed (below the 750 MB warning, 900 MB refusal and the 1 GB Pages limit). In a browser against the composed tree, Next pages and the playground issued no request outside/ExoJS/next/, carrynoindex, and pointer-to-world placement under zoom is exact.The local pre-push hook was bypassed for this branch: on Windows,
main's unit lane currently fails before and after this change because of the Vitest 5.0.5 bump (asequence.groupOrder/maxWorkersconflict between standalone and inheriting projects, and an unresolvable worker path interrain-worker-parity); Linux CI is unaffected. CI on this PR runs every lane because workflows changed.