Point release consumer dispatch at renamed policyengine-sim-api#467
Merged
Conversation
The consumer repo policyengine-api-v2 was renamed to policyengine-sim-api. actions/create-github-app-token (the installation access-token API) does not follow repo renames, so the release NotifyConsumers job failed with a 422 and never dispatched policyengine-release to consumers. Update the repo name in push.yaml (App token scope) and dispatch-policyengine-release.sh (CONSUMER_REPOS). The historical CHANGELOG.md entry is left as shipped-release history. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Fixes #466
Summary
The consumer repo
policyengine-api-v2was renamed topolicyengine-sim-api, which broke the post-release consumer-notification step in the release pipeline.Root cause
NotifyConsumers(.github/workflows/push.yaml) mints a GitHub App token scoped torepositories: policyengine-api,policyengine-api-v2, then runs.github/dispatch-policyengine-release.shto send apolicyengine-releaserepository dispatch to those repos.actions/create-github-app-token(the installation access-token API) does not follow repository renames, so requesting the old name returns:The job dies at token generation, before any dispatch. Confirmed on the
policyengine 4.20.2release (run 29043618022): Publish succeeded, but Open consumer update PRs failed, so no downstream repo received a version-bump PR.Change
push.yaml→repositories: policyengine-api,policyengine-sim-apidispatch-policyengine-release.sh→CONSUMER_REPOSusespolicyengine-sim-apiThe historical
CHANGELOG.mdentry that mentions the old name is intentionally left unchanged as shipped-release history.Note
This fixes releases going forward. It does not retroactively notify consumers for 4.20.2 (that dispatch already failed) — the sim API can be bumped to 4.20.2 now by manually running its
check-policyengine-updates.yml(workflow_dispatch, version4.20.2).🤖 Generated with Claude Code