Skip to content

ci: canonical registry notify (fix dead dispatch + drop manifest-overwrite)#33

Merged
intel352 merged 2 commits into
mainfrom
chore/canonical-registry-notify
Jun 1, 2026
Merged

ci: canonical registry notify (fix dead dispatch + drop manifest-overwrite)#33
intel352 merged 2 commits into
mainfrom
chore/canonical-registry-notify

Conversation

@intel352
Copy link
Copy Markdown
Contributor

@intel352 intel352 commented Jun 1, 2026

Replaces the broken notify-registry dispatch step with the fleet-canonical notify-workflow-registry job.

What changed:

  • Removed REGISTRY_PAT reference and old peter-evans/repository-dispatch@v3 step with full github.repository plugin name
  • Added dedicated notify-workflow-registry job: pinned SHA @28959ce (v4), repo_dispatch_token, bare plugin name "azure", and canonical if-guard (no deleted, no pre-release, correct repo)
  • Retained the notify-registry job's github-script step that flips GoReleaser draft releases to non-draft

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Replaces the old notify-registry dispatch step (REGISTRY_PAT, full
github.repository as plugin name, peter-evans/repository-dispatch@v3,
guarded by continue-on-error) with a dedicated notify-workflow-registry
job using the fleet-canonical shape:
- token: secrets.repo_dispatch_token
- client-payload plugin field: bare name "azure" (not github.repository)
- pinned SHA peter-evans/repository-dispatch@28959ce...  # v4
- if-guard: no deleted events, no pre-release tags, correct repo

The old REGISTRY_PAT reference is removed entirely; the publish-GitHub-
release github-script step is retained in its existing notify-registry
job unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 1, 2026 05:07
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the release workflow to replace the previously broken workflow-registry notification (which relied on a step-level env for its if guard) with a dedicated, pinned repository-dispatch job intended to follow the fleet “canonical” registry notification pattern.

Changes:

  • Removes the old peter-evans/repository-dispatch@v3 step that referenced REGISTRY_PAT and sent the full github.repository as the plugin identifier.
  • Adds a new notify-workflow-registry job that dispatches plugin-release to GoCodeAlone/workflow-registry using a pinned SHA and the bare plugin name ("azure").
  • Keeps the existing github-script step that flips GoReleaser draft releases to non-draft (but see comments about workflow_dispatch behavior).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +114 to +126
if: >-
!github.event.deleted
&& !contains(github.ref_name, '-')
&& github.repository == 'GoCodeAlone/workflow-plugin-azure'
steps:
- name: Trigger registry manifest sync
uses: peter-evans/repository-dispatch@28959ce8df70de7be546dd1250a005dd32156697 # v4
with:
token: ${{ secrets.repo_dispatch_token }}
repository: GoCodeAlone/workflow-registry
event-type: plugin-release
client-payload: |-
{"plugin": "azure", "tag": "${{ github.ref_name }}"}
Comment thread .github/workflows/release.yml Outdated
Comment on lines 80 to 82
@@ -82,18 +82,6 @@ jobs:
needs: [release]
Comment on lines 85 to 87
- name: Publish GitHub release
uses: actions/github-script@v7
with:
The job now only flips the release draft->non-draft; rename it for clarity
and chain notify-workflow-registry after it (needs: publish-release),
matching the rest of the fleet. No functional change to publishing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@intel352 intel352 merged commit 358fa7a into main Jun 1, 2026
5 checks passed
@intel352 intel352 deleted the chore/canonical-registry-notify branch June 1, 2026 05:25
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