Repository navigation
Conversation
This branch has not been deployed
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.
📥 Pull Request
📘 Description
The release workflow (
python-publish.yml) publishesagentopsto PyPI. Itsdeployjob holdsPYPI_API_TOKENandTEST_PYPI_API_TOKEN(plusid-token: write), and in that same job it runsastral-sh/setup-uv@v5, a tag that can be moved to other code at any time. If it is, that code runs next to the PyPI token.docker-mcp-publish.ymlhas the same pattern withDOCKERHUB_TOKENand the Docker actions on@v3/@v5.This PR adds GitHub's workflow dependency lockfile (
.github/workflows/actions.lock), generated with gh actions-lock. It records the commit behind every action (13 actions + 1 transitive, across the 9 workflows) and GitHub checks it at run time, so a moved tag can't change what runs..github/workflows/actions.lock.astral-sh/setup-uv@v5→@v5.4.2anddocker/login-action@v3→@v3.7.0. Onlyuses:lines change, no workflow logic.Not covered by a lockfile:
uv pip install buildin the release job resolves the latestbuildat each run.🧪 Testing
gh actions-lock --verify: "All 9 workflows valid".git diff: 0 changed lines outsideuses:(9 workflows +actions.lock).Found by Plumber's analysis, reviewed and submitted by me.