Repository navigation
ci(release): stop trying to publish the hermes plugin to PyPI - #5654
Merged
Merged
Conversation
This was referenced Oct 20, 2026
Merged
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
Hermes releases now take the plugin path in
release-integration.yml(no package to publish) instead of the Python/PyPI path.Why
NousResearch/hermes-agentplugin catalog, which pins this repo at a commit. Nothing pip-installs it.uv buildruns the plugin'ssetup.pyas a setuptools script, but that file is thehermes memory setupwizard and importsagent.secret_scope, which only exists inside Hermes.hermes-plugin-hindsightwas never published (PyPI returns 404), so no one depends on it. The oldhindsight-hermespackage stopped at 0.5.0 in March.The
pyproject.tomlstays: the test job uses it.