Update flatt-security/setup-takumi-guard-npm action to v1.2.0 - #1799
Merged
renovate[bot] merged 1 commit intoAug 18, 2026
Merged
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
renovate
Bot
deleted the
renovate/flatt-security-setup-takumi-guard-npm-1.x
branch
August 18, 2026 02:34
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.
This PR contains the following updates:
v1.1.1→v1.2.0Release Notes
flatt-security/setup-takumi-guard-npm (flatt-security/setup-takumi-guard-npm)
v1.2.0Compare Source
New Feature
audienceinput controls theaudclaim of the OIDC token requested for the bot token exchange. (#6)audchange: withaudienceunset, the token is now requested with the STS URL (https://sts.cloud.shisho.dev, normalized without a trailing slash) as its audience — previously the hardcoded registry hostnpm.flatt.tech. Built-in trust conditions do not validateaud, so existing setups are unaffected; CustomOIDC trust conditions using the default STS audience (e.g. GitHub Enterprise Server) start working without overrides.audienceexplicitly if your Bot trust condition expects a different value.Note:
v1has not moved yet — workflows trackingv1keep the previous behavior until the upcomingv1retag. Pinned tags are unaffected.Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.