Repository navigation
Automatically refresh the public download catalog after releases - #152
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
Independent catalog regeneration during Pages builds can invalidate the expected hash and cause verification timeouts.
1 open issue
What changed in this PR
Automates public download catalog updates after successful releases, replacing the manual website refresh.
Changes:
- Adds post-release synchronization with repository-scoped credentials.
- Validates releases, retries conflicting pushes, and verifies the CDN catalog.
- Documents deployment, recovery, and planned live validation.
| File | Description |
|---|---|
| openspec/changes/auto-refresh-public-downloads/tasks.md | Tracks implementation and pending validation. |
| openspec/changes/auto-refresh-public-downloads/specs/public-release-catalog/spec.md | Defines synchronization requirements. |
| openspec/changes/auto-refresh-public-downloads/proposal.md | Describes purpose and scope. |
| openspec/changes/auto-refresh-public-downloads/design.md | Records deployment design and risks. |
| openspec/changes/auto-refresh-public-downloads/.openspec.yaml | Declares change metadata. |
| docs/public-download-publishing.md | Documents operation and recovery. |
| .github/workflows/refresh-public-downloads.yml | Implements synchronization and CDN verification. |
| .github/workflows/package.yml | Invokes synchronization after release publication. |
Review effort: Balanced
| exit 1 | ||
|
|
||
| - name: Verify public CDN catalog | ||
| run: python scripts/wait_for_catalog.py public/aceupdate.json --timeout 900 |
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.
After a tagged GitHub Release publishes its installation assets, package.yml now calls a reusable workflow to refresh tmoonlight/acecode-site and verify the public CDN catalog. The website push uses a deploy key scoped to that repository and automatically starts Pages deployment.
The synchronization checks the published tag, required packages and SHA-256 values, serializes retries, and avoids empty commits. Existing packaging, model APIs and aupdate mirroring are unchanged.
Validation: website generator tests (5 passed), download catalog checks (104 releases / 1,165 assets), workflow syntax/dependency/permission checks, and strict OpenSpec validation. The existing v1.0.13 release completed the synchronization and Pages deployment; a second run succeeded without another commit.
The repository-wide R15 delayed-injection check still reports the pre-existing linux_desktop.cpp/.hpp findings, also present on base master 01d7421. This change does not modify those files.
OpenSpec: auto-refresh-public-downloads.