chore: bump nolte/gh-plumbing pin from v1.1.12 to v1.1.18#22
Merged
Conversation
PR #21 squash-merged as a merge commit because reusable-automerge.yaml at v1.1.12 did not set MERGE_METHOD=squash, so pascalgn/automerge-action fell back to its default 'merge' strategy. The fix shipped upstream in: - v1.1.13: MERGE_METHOD: squash (gh-plumbing#323) - v1.1.16: MERGE_DELETE_BRANCH: "true" (gh-plumbing#332) Bumping every reusable-workflow pin in this repo to v1.1.18 (the current latest tag) picks up both fixes and keeps the portfolio convention of tag-pinned reusable-workflow references intact. Touched workflows: - automerge.yaml - spelling.yaml - release-drafter.yml - release-publish.yml - release-cd-refresh-master.yml - release-cd-deliver-docs.yml - build-static-tests.yaml (3 references) Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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.
Summary
Bump every reusable-workflow pin in
.github/workflows/fromnolte/gh-plumbing@v1.1.12to@v1.1.18so that PRs squash-mergecorrectly and the merged source branch is deleted automatically.
Changes
reusable-automerge.yaml@v1.1.12→@v1.1.18reusable-spelling-vale.yaml@v1.1.12→@v1.1.18reusable-release-drafter.yml@v1.1.12→@v1.1.18reusable-release-publish.yml@v1.1.12→@v1.1.18reusable-release-cd-refresh-master.yml@v1.1.12→@v1.1.18reusable-mkdocs.yaml@v1.1.12→@v1.1.18reusable-pre-commit.yaml,reusable-trivy.yaml,reusable-chain-bench.yamlall@v1.1.12→@v1.1.18Linked issues
Refs nolte/gh-plumbing#345 (closed) — the original report assumed the
override was missing upstream; it was already in place since v1.1.13
(MERGE_METHOD: squash, gh-plumbing#323) and v1.1.16 (MERGE_DELETE_BRANCH,
gh-plumbing#332). The actual fix for this repo is the pin bump.
Refs #21 — the PR that landed as a merge commit because of the stale
pin. No retroactive fix; the next PR using
automerge.yaml@v1.1.18will squash-merge as the spec requires.
Testing
grep -rn "@v1\." .github/workflows/confirms every reference nowpoints to
@v1.1.18and no@v1.1.12reference remains.pre-commit run --all-files— passes (check-yaml,end-of-file-fixer, trailing-whitespace).
Risk / rollout notes
Low risk per release behaviour, but this PR is itself the first
real test of
automerge.yaml@v1.1.18in this repo: a successfulsquash-merge of this PR (single parent commit on develop instead of a
merge commit) confirms the bump fixed the symptom from #21. If this PR
also lands as a merge commit, open
workflow-healthtriage againstnolte/gh-plumbingagain with the run-log excerpt.No source-include changes; no API-shape changes. Consumer repos that
fetch
taskfile-include-*.yamlfrom this repository are not affected.