Skip to content

fix: declare exact dependency pins and quarantine exemptions - #24

Merged
ashmoonori-afk merged 1 commit into
ashmoonori-afk:mainfrom
ethernet8023:fix/hermes-quarantine-policy
Oct 6, 2026
Merged

ashmoonori-afk merged 1 commit into
ashmoonori-afk:mainfrom
ethernet8023:fix/hermes-quarantine-policy

Conversation

@ethernet8023

Copy link
Copy Markdown
Contributor

Hermes is proposing a 14-day dependency-release quarantine in NousResearch/hermes-agent#133409. this declares the plugin's exact direct package pin and explicit exemption so its reviewed release can install without exempting transitive packages.

summary

allow the reviewed plugin releases through hermes' 14-day quarantine without exempting transitive dependencies.

  • declare birkin-mnemosyne==0.4.0 as exact direct dependencies.
  • add [tool.uv.exclude-newer-package] entries set to false for only those packages.
  • preserve every dependency, extra and marker from the current upstream declaration.
  • add a metadata-only [project] in the catalog plugin directory; keep the existing manifest for older hosts.

verification

  • python 3.14.7: package and plugin imports pass.
  • current upstream main fails workspace resolution under the 14-day cutoff after removing the temporary core cutoffs.
  • focused upstream tests: 25 passed.
  • patched plugin: real core workspace lock, frozen sync, plugin import, exact-version checks and uv pip check pass.
  • full repository suites, external services and other platforms were not tested.

Infographic

upstream compatibility fixes

Declare reviewed exact releases and exempt only those direct packages.
Hermes keeps the global cutoff for transitive dependencies and rejects
exemptions for packages held by its core lock.
@ashmoonori-afk

Copy link
Copy Markdown
Owner

APPROVED at c1b9764

Independent review completed.

  • PyPI currently publishes non-yanked birkin-mnemosyne 0.4.0; this matches the existing plugin.yaml exact pin.
  • Official uv documentation confirms that exclude-newer-package = false exempts only the named package from the global cutoff. No broad exemption, alternate index/source, script, build hook or secret was added. The pinned package has no unconditional runtime dependencies.
  • With uv 0.11.8 / Python 3.13.13, the plugin directory successfully ran uv lock and uv sync --locked under --exclude-newer "14 days". The resulting lock retains P14D and only the named exemption; the installed version is 0.4.0, public memory/frontmatter imports and uv pip check pass, and artifact hashes match PyPI. Overriding the package exemption with a 14-day cutoff correctly fails resolution because 0.4.0 is newer than the cutoff.
  • Root packaging metadata and its explicit setuptools package list are unchanged. Existing root pip installs ran successfully in CI; the new nested metadata does not alter normal root pip/uv installation.
  • Run 37363010378 passed all 13 checks on this head, including non-gating extras. I read actual pytest execution logs on Ubuntu, Windows and macOS: six core jobs (657 passed, 3 existing optional skips each), four MCP jobs (684 passed, 2 existing optional skips each), three semantic jobs (679 passed, 1 existing optional skip each). No unresolved review threads.

Scope: reproduced the inexpensive standalone plugin lock/sync path, not the author's full patched Hermes workspace. No contributor-branch changes or release. Review environment cleaned up.

Documentation: https://docs.astral.sh/uv/reference/settings/#exclude-newer-package
Release metadata: https://pypi.org/pypi/birkin-mnemosyne/0.4.0/json

@ashmoonori-afk
ashmoonori-afk merged commit ba17f71 into ashmoonori-afk:main Oct 6, 2026
13 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