Skip to content

Pin the release and CI workflow actions to commit SHAs - #369

Merged
devin-ai-integration[bot] merged 1 commit into
mainfrom
devin/1794936757-zepai-4345-pin-release-actions
Nov 17, 2026
Merged

devin-ai-integration[bot] merged 1 commit into
mainfrom
devin/1794936757-zepai-4345-pin-release-actions

Conversation

@paul-paliychuk

@paul-paliychuk paul-paliychuk commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The release workflow publishes zep-cloud to 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 as getzep/graphiti:

actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5
pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

release-cloud.yml also has these changes:

  • The job permission is contents: read, not contents: write. The job does not write to the repository.
  • The checkout step sets persist-credentials: false. The job does not push.
  • The Poetry cache is removed from the release job, so a cache entry from another workflow cannot change the release build.

The publish step keeps the default attestations: true, so each release file gets a PyPI Publish attestation. ci.yml gets the same action pins, a top-level permissions: contents: read, and persist-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 build with Poetry 1.8.3, which is the release workflow version: the build made zep_cloud-4.1.0.tar.gz and zep_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:

  1. On PyPI, open the zep-cloud project, then Publishing. Add a Trusted Publisher with owner getzep, repository zep-python, workflow release-cloud.yml, and environment release.
  2. Publish one release. Make sure that the attestation shows environment release. Then remove the old publisher entry that has no environment.
  3. Revoke each PyPI API token that has upload access to zep-cloud or graphiti-core.
  4. In this repository, open Settings > Environments > release. Add one or more required reviewers. Set the deployment branches and tags to selected tags with the pattern v*. Do not allow administrators to bypass these rules.

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>
@devin-ai-integration

Copy link
Copy Markdown
Contributor

I'll fix CI failures and address comments from users with write access that start with 'Devin'.

  • Disable automatic comment, CI, and merge conflict monitoring

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@devin-ai-integration
devin-ai-integration Bot merged commit 7b751f9 into main Nov 17, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants