Skip to content

ci: use elevated token for API Guard#25

Merged
KochC merged 1 commit intodevfrom
ci/use-elevated-token-for-api-guard
Mar 16, 2026
Merged

ci: use elevated token for API Guard#25
KochC merged 1 commit intodevfrom
ci/use-elevated-token-for-api-guard

Conversation

@flxapps
Copy link
Copy Markdown

@flxapps flxapps commented Mar 16, 2026

Replaces 'inherit' with explicit token declaration in api-guard secrets for build workflows.

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 build workflows to stop using secrets: inherit for the api-guard reusable workflow call and instead pass an explicit elevated token.

Changes:

  • Replaced secrets: inherit with an explicit secrets.token: ${{ secrets.ELEVATED_TOKEN }} mapping in the main build workflow.
  • Replaced secrets: inherit with an explicit secrets.token: ${{ secrets.ELEVATED_TOKEN }} mapping in the dev build workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/build_main.yaml Updates secrets passing for the api-guard reusable workflow call (currently with incorrect indentation).
.github/workflows/build_dev.yaml Updates secrets passing for the api-guard reusable workflow call (currently with incorrect indentation).

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

You can also share your feedback on Copilot code review. Take the survey.

@github-actions
Copy link
Copy Markdown

Version Analysis

Next Version: 3.0.0-5

Changelog: 📄 View detailed changelog in job summary

Badge:
Version Badge

@flxapps flxapps force-pushed the ci/use-elevated-token-for-api-guard branch from e148b88 to bfd49ce Compare March 16, 2026 10:33
@flxapps flxapps requested a review from Copilot March 16, 2026 10:33
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 adjusts the build workflows’ reusable api-guard job to pass an explicit elevated token secret rather than inheriting all caller secrets, aligning with the API Guard workflow’s expected secret name.

Changes:

  • Replace secrets: inherit with an explicit secrets.token: ${{ secrets.ELEVATED_TOKEN }} mapping for the api-guard job in main builds.
  • Apply the same explicit secret mapping for the api-guard job in dev builds.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/build_main.yaml Passes ELEVATED_TOKEN explicitly to the reusable API Guard publish workflow as token.
.github/workflows/build_dev.yaml Passes ELEVATED_TOKEN explicitly to the reusable API Guard publish workflow as token.

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

You can also share your feedback on Copilot code review. Take the survey.

@github-actions
Copy link
Copy Markdown

Version Analysis

Next Version: 3.0.0-5

Changelog: 📄 View detailed changelog in job summary

Badge:
Version Badge

@KochC KochC merged commit dd70794 into dev Mar 16, 2026
8 checks passed
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.

3 participants