Repository navigation
release: 0.2.4 - #14
Merged
Merged
Conversation
Version 0.2.4 with what merged since 0.2.3: - #12: a policy replaced through the API survives a restart (saved under SENTINEL_DATA_DIR/policies, serialized, atomic) and every reload is recorded as a PolicyChanged span (review F21). - #11: retention no longer keeps forever the traces whose span timestamps were left empty by 0.2.2 after a rollback. - #13: versions.lock past new advisories (certifi, which ships in the container image, and the filelock/virtualenv pre-commit tooling). The CHANGELOG [0.2.4] section opens with an upgrade note: no configuration changes; back up the new policies directory with the database (compose already keeps it on the data volume); and a rollback to 0.2.3 ignores saved policies and cannot replay policy-change runs. 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.4, shipping what merged since 0.2.3:
POST /tenants/{tenant}/policysurvives a restart, and every reload is recorded as aPolicyChangedspan (review F21).versions.lockpast new advisories (certifi, which ships in the container image; filelock and virtualenv for pre-commit).Changes:
pyproject.toml0.2.3 → 0.2.4, the release workflow's example tag, and the CHANGELOG[Unreleased]section becomes[0.2.4] — 2026-10-24with an upgrade note (no configuration changes; back uppolicies/with the database; what a rollback to 0.2.3 does).After merging
Tag
v0.2.4on the merge commit;release.ymlre-runs lint, types and tests, checks the tag matchespyproject.toml, and waits for thepypiapproval before uploading.Testing
ruff,mypy --strictclean;check_versions_lock.py0 conflicts.python -m buildmakessentinel_prox-0.2.4;twine checkpasses the sdist and the wheel.Security invariants
🤖 Generated with Claude Code