Repository navigation
release: 0.2.3 - #10
Merged
Merged
Conversation
Version 0.2.3: the catalogue fixes merged in #8 (atomic Cosmos writes, explicit fail-closed checks, a Cosmos extra that lets Cosmos persistence start at all, indexed SQLite timestamps, verb-based attack labels) and the project site, README and community files merged in #9. Publishing it also refreshes the PyPI page, which still shows the 0.2.2 README and project URLs. The CHANGELOG [0.2.3] section opens with an upgrade note: no configuration changes; Cosmos users need the extra; and the SQLite store migrates in place, so a rollback should restore a backup rather than run 0.2.2 on the migrated file, because spans 0.2.2 writes get no value in the new timestamp column and upgrading again does not fill it in. It also names the two removed helpers, create_cosmos_store and build_web_server. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 and why
Cuts 0.2.3, which ships what merged since 0.2.2:
create_item), explicit fail-closed checks instead ofassert, asentinel-prox[cosmos]extra (without it Cosmos persistence could not start), indexed SQLite timestamps, and attack labels from tool-name verbs for any server.Changes:
pyproject.toml0.2.2 → 0.2.3, the release workflow's example tag, and the CHANGELOG[Unreleased]section becomes[0.2.3] — 2026-10-19, with an upgrade note:cosmosextra.tscolumn, and upgrading again does not fill it in (the backfill only runs when the column is missing). Checked against both versions' code.create_cosmos_store,build_web_server); only one was in the changelog.After merging
The tag publishes:
git tag -a v0.2.3 -m "..." && git push origin v0.2.3startsrelease.yml, which re-runs lint, types and tests, checks that the tag matchespyproject.toml, and waits for approval on thepypienvironment before uploading.Testing
versions.lock(mcp 1.30.0):pytest688 passed, 12 skipped (quarantined real-MCP diagnostics), 1 expected xfail.ruffandmypy --strictclean.scripts/check_versions_lock.py: 0 conflicts.python -m buildmakessentinel_prox-0.2.3(sdist and wheel);twine checkpasses both. The sdist holds onlysrc,testsand metadata (nowebsite/ornode_modules). The wheel's metadata has version 0.2.3 and the new project URLs.Security invariants
🤖 Generated with Claude Code