Skip to content

fix: enforce locked action dependencies #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
atharvmantri merged 1 commit into from
Sep 14, 2026
Merged

fix: enforce locked action dependencies #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,6 @@ runs:
args+=(--strict)
fi

uv run --project "$GITHUB_ACTION_PATH" memoryguard "${args[@]}"
# Fail if the action's committed dependency lock is stale instead of
# resolving a different graph during a user's CI run.
uv run --locked --project "$GITHUB_ACTION_PATH" memoryguard "${args[@]}"
6 changes: 4 additions & 2 deletions docs/github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,10 @@ enable strict mode:
```

For production workflows, pin `uses` to a reviewed commit instead of `main`.
The action uses `uv` to run the source in the action checkout; it does not
publish or install a package from PyPI.
The action uses `uv` and the repository's committed lockfile to run the source
in the action checkout; it does not publish or install a package from PyPI. If
the lockfile is stale, the action fails rather than silently resolving a new
dependency graph in CI.

## What the action does

Expand Down
Loading