Restore registry-sync so the catalog is rebuilt and signed again - #235
Merged
Merged
Conversation
The file left the repo on 2026-09-22 and the sync marked its executor obsolete, so nothing has rebuilt or signed the catalog since. Three submissions changed after that and are stale in the committed catalog. Restored as it was, except pnpm now comes from packageManager and the actions use the majors the rest of the repo uses. Documents the signing secret it needs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Reviewer's GuideRestores the registry-sync automation with current action versions and signing-secret support, allowing stale catalog packages to be rebuilt and reviewed without committing unsigned artifacts; adds operational guidance for running and securing the process. Sequence diagram for signed registry catalog synchronizationsequenceDiagram
participant Trigger
participant Workflow as registry-sync.yml
participant Build as build-catalog
participant Signing as SigningSecret
participant GitHub as GitHubPR
participant Deploy as deploy-storefront
Trigger->>Workflow: Trigger sync
Workflow->>Workflow: Decide pinned or latest mode
Workflow->>Build: build-catalog --update [--latest]
Signing-->>Build: AZPHALT_PACKAGE_SIGNING_KEY
Build-->>Workflow: Rebuild signed packages and catalog
Workflow->>Workflow: build-previews
Workflow->>GitHub: Open draft catalog PR
GitHub-->>Deploy: Merge catalog PR
Deploy->>Deploy: Rebuild and redeploy storefront
Flow diagram for registry sync modes and triggersflowchart TD
A[Sync trigger] --> B{Trigger type}
B -->|sources.json or submissions push| C[pinned mode]
B -->|schedule or extension-updated dispatch| D[latest mode]
B -->|manual workflow run| E{Selected mode}
E -->|pinned| C
E -->|latest| D
C --> F[Rebuild catalog with pinned refs]
D --> G[Re-pin sources, then rebuild catalog]
F --> H[Regenerate previews]
G --> H
H --> I{Registry changed?}
I -->|yes| J[Commit branch and open catalog PR]
I -->|no| K[Exit without PR]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
Owner
Author
OpenCode security review |
HereLiesAz
marked this pull request as ready for review
September 27, 2026 22:20
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @HereLiesAz, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 23 hours and 6 minutes by commenting @sourcery-ai review. Upgrade to get a review now.
This branch had an error being deployed
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
2 participants
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.
Why
build-catalog --checkfails forcom.azphalt.example.hello-lut,com.hereliesaz.guillotine.cool-noirandcom.hereliesaz.guillotine.teal-orange.capabilities(asset packages declare none) but nothing rebuilt them, because.github/workflows/registry-sync.ymlleft the repo on 2026-09-22. The workflows sync then marked its executor obsolete.What
.github/workflows/registry-sync.ymlis restored from the registered source (registry/1296954472/registry-sync-9340fed1.source.ymlin HereLiesAz/workflows). Only two things changed:pnpm/action-setupno longer pins9.15.0. It readspackageManager(pnpm 12), and naming both makes the action refuse to run.docs/OPERATIONS.mdgets a new section, "Rebuilding and signing the catalog": what triggers the workflow, where it runs, the signing secret it needs, and a rule never to commit an unsigned rebuild of a signed package.After merging (user-side)
azphalt-registry-sync.yml, which is still grandfathered), and replaces this file with a tracker.azphalt, setAZPHALT_PACKAGE_SIGNING_KEY(and optionallyAZPHALT_PACKAGE_SIGNING_KEY_ID).pinnedmode. It rebuilds the three stale packages signed and opens the catalog PR.Verification
capabilities, plus the droppedsignature.jsona local unsigned rebuild would produce. I left the committed bytes untouched.🤖 Generated with Claude Code
https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv
Generated by Claude Code
Summary by Sourcery
Restore automated, signed catalog synchronization and document the operational requirements for safely publishing rebuilt packages.
New Features:
Bug Fixes:
Enhancements:
CI:
Documentation: