ci(ingestion): add manual package release workflow - #585
Merged
Conversation
There was a problem hiding this comment.
Critical
- .github/workflows/release-ingestion.yml:184 — If a GitHub Release exists but its Git tag was deleted,
TAG_EXISTSremains false whilegh release viewsucceeds. The workflow then skips tag creation and publishes to PyPI without a validated source tag, despite claiming the release is “at the validated commit.” Fix by failing when the release exists without its tag, or recreate the tag atRELEASE_SHAand verify it before publishing.
mehulp93
force-pushed
the
feat/manual-ingestion-release
branch
from
July 30, 2026 01:40
d1a6fc4 to
d5a2702
Compare
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
1 participant
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
zep-ingestreleases manual-only throughworkflow_dispatchmainand match the version declared iningestion/pyproject.tomlWhy
The ingestion package release workflow previously required a GitHub Release to be published before its validation and publishing jobs could run. A manual workflow provides the same operator-driven release path as the repository's other release automation while preserving exact-source, version, and tag validation.
Validation
git diff --check