Repository navigation
Pin the release and CI workflow actions to commit SHAs - #369
Merged
devin-ai-integration[bot] merged 1 commit intoNov 17, 2026
Merged
devin-ai-integration[bot] merged 1 commit into
devin-ai-integration[bot] merged 1 commit into
Conversation
The release workflow publishes zep-cloud to PyPI with an OIDC token. A mutable action tag can change the code that runs with that token. This commit pins each action to a full commit SHA, with the same pins as getzep/graphiti. It also removes the Poetry cache from the release job, sets the release job to contents: read, and stops the checkout from keeping the GitHub token. Refs ZEPAI-4345. Co-Authored-By: Paul <paul@getzep.com>
Contributor
|
I'll fix CI failures and address comments from users with write access that start with 'Devin'.
|
7 of 15 tasks
jackaldenryan
approved these changes
Nov 17, 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
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
The release workflow publishes
zep-cloudto PyPI with a short-lived OIDC token (Trusted Publishing). Before this change, the workflow used mutable action references (@v4,@v5,@release/v1). A change to one of those tags could change the code that runs with the publish token. This change pins each action to a full commit SHA, with the same pins asgetzep/graphiti:release-cloud.ymlalso has these changes:contents: read, notcontents: write. The job does not write to the repository.persist-credentials: false. The job does not push.The publish step keeps the default
attestations: true, so each release file gets a PyPI Publish attestation.ci.ymlgets the same action pins, a top-levelpermissions: contents: read, andpersist-credentials: false.Validation
actionlint .github/workflows/*.yml: no errors.zizmor --offline .github/workflows/: "No findings to report." Before this change, it reported 1 high finding (cache poisoning) and several unpinned-action and permission findings.poetry buildwith Poetry 1.8.3, which is the release workflow version: the build madezep_cloud-4.1.0.tar.gzandzep_cloud-4.1.0-py3-none-any.whl.Steps that need a person
These steps are not in this PR. A PyPI owner and a repository administrator must do them:
zep-cloudproject, then Publishing. Add a Trusted Publisher with ownergetzep, repositoryzep-python, workflowrelease-cloud.yml, and environmentrelease.release. Then remove the old publisher entry that has no environment.zep-cloudorgraphiti-core.v*. Do not allow administrators to bypass these rules.