Repository navigation
fix: separate session-store retirement owners and blockers - #384
Merged
Merged
Conversation
devSejung
marked this pull request as ready for review
October 23, 2026 21:33
devSejung
force-pushed
the
fix/session-store-compat-retirement
branch
from
October 24, 2026 12:09
897f5b1 to
56e4d44
Compare
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.
Closes #383
Related: #290
What Problem This Solves
Resolves a problem where compatibility reviewers see four beta.5 plugin SDK helpers and two package-root doctor aliases grouped under one SDK owner, despite their different removal conditions. Plain package-root helper labels also omit those aliases from the report's existing token-based reference search.
Why This Change Was Made
Split SDK and core retirement records at their existing source-owned boundaries. Both retain the original October 12 review date, verified published-reader migration, and explicit breaking-release approval. SDK removal additionally requires exclusion of beta.5 from the supported plugin floor; package-root removal requires the v2026.7.x legacy doctor upgrade window to close. Runtime exports, support floors, and failure predicates are unchanged.
This branch is refreshed onto main
59d800dd70b7924810467b440f367bf28dfb423b. Main #376 already fixed the original conditional-record classification and Zod security failure. The remaining diff is the owner/blocker split and report coverage; no dependency or security-guard change is added here.User Impact
Maintainers can review the two retirement tasks independently, with visible dates, blockers, and heuristic references. References remain triage evidence, not proof that published plugin consumers have migrated. Genuine unconditional expirations still fail CI.
Evidence
897f5b120cf323e6142f118b27347c572ce97ef2failed security-fast on GHSA-mrhx-c7xc-m3w5. The refreshed source inherits main's reviewed remediation; the exact commandnode scripts/pre-commit/pnpm-audit-prod.mjs --audit-level=highpassed live on Ubuntu 22.04.5 / Node 24.18.0 / pnpm 11.15.1 at UTC 2026-10-24 11:41:24.56e4d440cb48e09c5d361b652a37c88d10873699; Linux checked tree0c2c8efea4f4de21b9df5cb3e6e6c34d7d876152matches the committed tree. Exact-head CI completed successfully: 54 jobs passed, 13 intentionally skipped, zero failures. The original failing security-fast job, lint, and openclaw/ci-gate all passed.