Skip to content

Mark the October 27 security plan merged - #724

Open
sambitcreate wants to merge 2 commits into
mainfrom
claude/project-thread-hcvmmd
Open

sambitcreate wants to merge 2 commits into
mainfrom
claude/project-thread-hcvmmd

Conversation

@sambitcreate

Copy link
Copy Markdown
Owner

Requested by sbt · project thread

Summary

The October 27 security remediation stack has landed. #608 through #614 merged on November 3, 2026, after #604, #606 and #607 (in 0.63.0). #605 was closed because Telegram is being removed. This updates the plan's status line and its row in docs/plans/README.md to match. The plan stays in docs/plans/ because release and device acceptance are still separate steps.

Docs only, no code changes.


Generated by Claude Code

#608 to #614 merged on November 3, 2026, after #604, #606 and #607.
#605 was closed. Release and device acceptance stay separate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018VA6RHWP6kkCRLYaa5exc8

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

The merged-stack status is accurate, but the plan's acceptance ledger remains stale and should be reconciled before this documentation update merges.

Reviewed changes the plan-index row and security-plan status line were checked against the referenced pull requests, release inventory, and the plan's remaining acceptance gates.

  • Plan index — Changes the October 27 security remediation entry from in progress to merged, distinguishing shipped, unreleased, and separately tracked acceptance work.
  • Plan status — Records #604 and #606 through #614 as merged, #605 as closed, and preserves the release/device-acceptance distinction.

Pullfrog  | ⚠️ this action is pinned to a commit SHA, which freezes the cleanup step — switch to @v0 or keep the SHA fresh with Dependabot | Fix all ➔ | Fix 👍s ➔ | View workflow run | Using GPT Sol | 𝕏

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes since the prior Pullfrog review, I checked the dated merge ledger and remaining acceptance gates against GitHub’s PR metadata and the plan’s completion criteria.

  • Recorded the merged stack — Added each landed slice’s exact head, merge commit, and merge date, while identifying the older execution entries as pre-merge snapshots.
  • Preserved outstanding acceptance — Kept packaged-app, physical-device, live-network/proxy/custom-TLS, release, deferred protocol, and publisher-verification work open rather than treating merge as full acceptance.

Pullfrog  | ⚠️ this action is pinned to a commit SHA, which freezes the cleanup step — switch to @v0 or keep the SHA fresh with Dependabot | View workflow run | Using GPT Sol | 𝕏

This branch has not been deployed

No deployments
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