Bump github/gh-aw-actions/setup from 0.87.5 to 0.88.0 in the github-actions group - #6513
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the github-actions group with 1 update: [github/gh-aw-actions/setup](https://github.com/github/gh-aw-actions). Updates `github/gh-aw-actions/setup` from 0.87.5 to 0.88.0 - [Release notes](https://github.com/github/gh-aw-actions/releases) - [Changelog](https://github.com/github/gh-aw-actions/blob/main/CHANGELOG.md) - [Commits](github/gh-aw-actions@2a78d04...afc709f) --- updated-dependencies: - dependency-name: github/gh-aw-actions/setup dependency-version: 0.88.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
ranm-msft
left a comment
There was a problem hiding this comment.
Recommending this be closed rather than merged - gh-aw's own documentation says so explicitly. The pin itself is correct (I verified afc709f45ed6a3f756eb4551856c6a9c42e15b2c is tag v0.88.0); the problem is the update path.
From gh-aw's compilation-process reference: "Dependabot may open PRs to bump github/gh-aw-actions to a newer SHA. Do not merge them - pin updates must come from gh aw compile, which coordinates pins across all compiled workflows from a single release."
These .lock.yml files are generated artifacts headed DO NOT EDIT. This PR rewrites the 11 executable uses: references and nothing else, so duplicate-surfacing.lock.yml ends up describing the same action three ways: the machine-readable gh-aw-manifest and compiler_version say v0.83.4, the generated "Custom actions used" inventory says v0.87.1, and the runtime pins would say v0.88.0. That drift predates this PR, but this widens it rather than repairing it. Worth noting frontmatter_hash/body_hash cover the source .md, so no freshness check will flag it.
I would stop short of claiming v0.88.0 is demonstrably broken against v0.83.4-generated output - only that it is an uncoordinated pairing outside the supported model, and a later compile will regenerate these pins rather than preserve them.
One useful detail: the docs note gh aw compile auto-inserts the ignore rule when a github-actions block already exists in .github/dependabot.yml. Ours has the block but no ignore rule, so a recompile should fix both the pins and the recurrence in one step.
Bumps the github-actions group with 1 update: github/gh-aw-actions/setup.
Updates
github/gh-aw-actions/setupfrom 0.87.5 to 0.88.0Release notes
Sourced from github/gh-aw-actions/setup's releases.
Commits
afc709fchore: sync actions from gh-aw@v0.88.0 (#224)bc8c008chore: sync actions from gh-aw@v0.87.10 (#222)49dc896chore: sync actions from gh-aw@v0.87.9 (#220)1aa033cchore: sync actions from gh-aw@v0.87.6 (#219)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions