ci: fix release automation dispatch#20
Merged
Merged
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
alphakenz
approved these changes
Jun 1, 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.
What
Fix release automation so future version bump merges do not depend on a tag push created by GITHUB_TOKEN to trigger a separate workflow.
Changes:
Also completed the missing v0.1.5 GitHub Release manually from the existing tag: https://github.com/KnowGuard-AI/HotMem/releases/tag/v0.1.5
Why
PR #19 merged on May 28, 2026 and Auto Tag did run, but it found v0.1.5 already existed and skipped tag creation. Since no new tag was pushed, release.yml did not run. There is also a future reliability issue: workflows triggered by GITHUB_TOKEN-created events may be suppressed by GitHub, so chaining release publication only from the auto-created tag push is brittle.
The current PyPI v0.1.5 page was built from the older v0.1.5 side tag, so its metadata can look stale. PyPI does not allow replacing already-published distribution files for the same version. This PR ensures the next release builds from the checked-out release tag and fails before upload if README.md is not included as the package long description.
Verification