feat: support DSH 0.2 persistence handles - #1
Merged
Merged
Conversation
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.
DSH
0.2.0-rc.1removes the coordinator and ID-addressed persistence API used by the current plugin. This updates Session Teleport to the publishedcreate/open → SessionHandlecontract and pins its development baseline to DSH0.2.0-rc.1/ Cordis4.0.4.inheritedEventCountacross storage and export/import, and support empty session materialization/import/rollback. Schema 5 adds the inherited boundary without rewriting stored events. Upgrade the authority service and adapter together; a readiness check refuses older services. The adapter refuses retired session formats rather than silently relabeling them as format 4.Validation on macOS with Node 24:
pnpm checkwith the official DSH CLI: 57 passed, 6 PostgreSQL-only tests skipped; includes strict type checks, build, release artifact checks, actual loader/capture probes, and a real JSONL fork export/import/restore.pnpm audit --prod: no vulnerabilities.pnpm pack:check: passed (90 files, no local npm config).The two-commit lifecycle probe using old
0.6.0-rc.2as the starting version stopped at the new DSH compatibility guard: DSH 0.2 correctly refuses that old plugin before installation and restores the disposable profile. No version exemption was enabled. The completed package/loader checks validate the new candidate; cross-runtime upgrades from an already installed RC.6 profile still need their own acceptance run.Physical multi-host/WAN, database failover, and Windows operation remain outside this validation; this PR does not certify those release gates.