Skip to content

ci(ingestion): publish to PyPI before creating the release tag - #602

Merged
jackaldenryan merged 1 commit into
mainfrom
jack/fix-ci-failure
Aug 12, 2026
Merged

ci(ingestion): publish to PyPI before creating the release tag#602
jackaldenryan merged 1 commit into
mainfrom
jack/fix-ci-failure

Conversation

@jackaldenryan

Copy link
Copy Markdown
Contributor

Summary

  • Reorders the ingestion release job so PyPI upload happens before the GitHub tag/release is created.
  • Prevents a failed upload from leaving an orphaned tag that blocks the next dispatch after main moves.

Test plan

  • Merge, then re-dispatch Release Ingestion Package from main
  • Confirm zep-ingest 0.2.0 publishes to PyPI and the GitHub release/tag is created afterward

Made with Cursor

A failed upload previously left an orphaned tag that blocked re-dispatch after main moved.

Co-authored-by: Cursor <cursoragent@cursor.com>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

  • Critical — .github/workflows/release-ingestion.yml, added “Download build artifacts” step before actions/checkout: actions/checkout cleans/prepares the workspace and will remove the untracked dist/ directory downloaded immediately before it. The subsequent PyPI action therefore has no packages to publish, causing every release to fail. Move checkout before artifact download, or download artifacts under ${{ runner.temp }} and publish from there.

  • Critical — same hunk, publishing before GitHub release creation: If PyPI publication succeeds but checkout or gh release create fails, rerunning the workflow attempts to upload the immutable version again. PyPI rejects duplicate distributions, so the retry never reaches release creation, leaving the release permanently incomplete. Make publication retry-safe (for example, skip-existing: true with appropriate validation) or redesign the ordering/rollback behavior so a rerun can finish the GitHub release.

@jackaldenryan
jackaldenryan merged commit be263ee into main Aug 12, 2026
10 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.

1 participant