ci(LINCHPIN-5510): Follow linchpin/docspress@v1 instead of a pinned SHA - #77
Open
aaronware wants to merge 1 commit into
Open
ci(LINCHPIN-5510): Follow linchpin/docspress@v1 instead of a pinned SHA#77aaronware wants to merge 1 commit into
aaronware wants to merge 1 commit into
Conversation
That pin was 3 commits behind. It already carried the non-JSON response reporting; this is about not falling further behind. A SHA pin defends against a third party repointing a tag under you. This is our own fork, in our own organisation, behind branch protection, consumed only by our own repositories: the same trust boundary, so the pin defends against nothing while guaranteeing we miss its fixes. actions/checkout stays pinned. It is genuinely third party and this job holds a WordPress token. Refs: https://app.clickup.com/t/LINCHPIN-5510 Co-Authored-By: Claude Opus 5 (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.
ClickUp: https://app.clickup.com/t/LINCHPIN-5510
This repository's pin was 3 commits behind
main. It already carried the non-JSON response reporting, so this is about not falling further behind rather than recovering a missing fix.SHA pinning defends against a third party repointing a tag under you.
linchpin/docspressis our own fork, in our own organisation, behind branch protection, consumed only by our own repositories — the same trust boundary. The pin defends against nothing here while guaranteeing we miss its fixes.v1is tagged at71b8582and moves forward as fixes and backwards-compatible inputs land. Anything that removes or repurposes an input, or changes what a run writes to WordPress, becomesv2so existing workflows keep working until they opt in. Contract and the commands to move the tag are in the fork's README.actions/checkoutstays pinned: genuinely third party, and this job holds a WordPress token.Companion: linchpin/docspress#7 adds CI to the fork — it had none — so a merge to its
main, which is now a merge to production for every repository here, is linted and tested first.Part of a sweep across all seven consuming repositories.
🤖 Generated with Claude Code