ci: pin ad-m/github-push-action to a full commit SHA in the release job#3677
Merged
Merged
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
wjones127
approved these changes
Jul 16, 2026
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
2 participants
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.
Hi, and thank you for LanceDB.
Small CI supply-chain hardening. In
make-release-commit.yml, the release job checks out withLANCEDB_RELEASE_TOKEN(a push-capable PAT) and its final step pushes the version tag using a third-party action pinned to a mutable branch:@mastercan move after review; whatever it points at then runs with that release token in scope. This PR pins it to the commit behind the current release (v1.3.0→881a6320…), keeping the version visible as a comment. Behavior today is unchanged.For transparency: I used AI assistance to spot and draft this; I verified the workflow and resolved the SHA myself.