Repository navigation
fix(pages): preserve the released resource catalog - #209
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
SSC-STUDIO
enabled auto-merge
October 10, 2026 13:05
SSC-STUDIO
had a problem deploying
to
github-pages
October 10, 2026 13:05 — with 
GitHub Actions
Failure
GitHub Actions
Failure
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
1 participant
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.
After v6.1.4 published successfully, the live stable resource catalog still reported 5.0.1. Pages copied the release artifact first and then overwrote its current catalogs with archived repository resources.
Copy repository resources first, then overlay the newest successful Release's Pages artifact and derive the compatibility catalog from that final result. Download only
pages-resources-v*rather than every release artifact. Installer assets and the v6.1.4 tag stay unchanged.Validation: three tests execute the deployed PowerShell assembly with local fixtures, covering release-triggered deployment, site-only redeployment, retained archived packs, compatibility alias equality and fallback without a successful release. All three pass, and the repository Unicode check passes.