Skip to content

fix(ci): use MP_SEMANTIC_RELEASE_BOT for release workflow#77

Closed
alexs-mparticle wants to merge 1 commit intodevelopmentfrom
fix/nojira-release-token
Closed

fix(ci): use MP_SEMANTIC_RELEASE_BOT for release workflow#77
alexs-mparticle wants to merge 1 commit intodevelopmentfrom
fix/nojira-release-token

Conversation

@alexs-mparticle
Copy link
Collaborator

Summary

  • Replace MP_INTEGRATIONS_SEMANTIC_RELEASE_BOT with MP_SEMANTIC_RELEASE_BOT in the release workflow
  • The old PAT is expired/revoked and causes a 404 when @semantic-release/github tries to create a GitHub Release
  • This is an org-wide issue affecting all JS kits (GA4, GTM, etc.) — confirmed MP_SEMANTIC_RELEASE_BOT works via test on the doubleclick repo
  • Updated both the release job (GITHUB_TOKEN env) and the sync-repository job (checkout token)

Test plan

  • Run the release workflow with dryRun: true to confirm it passes
  • Run the release workflow with dryRun: false to confirm GitHub Release is created successfully

The MP_INTEGRATIONS_SEMANTIC_RELEASE_BOT PAT is expired/revoked and
causes a 404 when semantic-release tries to create a GitHub Release.
Switch to MP_SEMANTIC_RELEASE_BOT which has valid write access.
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.

1 participant