Every push to main since 10-29 21:57 UTC has failed the Handle Versions job, so the Version Packages PR has stopped updating and nothing has been released. The cause is one pending changeset that bumps @phaseo/factory, a package that no longer exists. This PR removes that line.

What changed

• .changeset/security-alerts-round2-20261029.md now bumps only @phaseo/desktop. The @phaseo/factory line is gone.

Why

The "Create release PR / publish" step fails in pnpm run changeset:version (run 41050266135, job 124050188072):

🦋 changeset v3.0.2
Error: Found changeset security-alerts-round2-20261029 for package @phaseo/factory which is not in the workspace
    at mapGetOrThrow (.../@changesets/assemble-release-plan/dist/index.mjs:35:27)
🦋 Exited with code 1

Two PRs that merged close together caused it:

• #3396 (a9392d5e5c, 21:26 UTC) added this changeset for @phaseo/desktop and @phaseo/factory. Its CI run, 40957799155, is the last green one.
• #3395 (0a93ac0b68, 21:57 UTC) merged Factory into desktop and deleted apps/factory. It removed @phaseo/factory from the two changesets it knew about but not from this new one. Its run, 40961995959, was the first to fail.

All 11 main runs since then have failed this job with the same error.

How

Delete the stale package line. The desktop patch and its note stay as they are, since the Factory code now ships inside desktop.

Not changed:

• PR-time changeset status check. It would catch a race like this before merge, but it's a separate decision and not needed for this fix.
• untracked working tree files would be overwritten warning. It's about a devtools-viewer asset and also appears in the last successful run, so it isn't the cause.

Before and after

Verification

• Reproduced the CI error locally with pnpm dlx @changesets/cli@3.0.2 status, applied the fix, and ran it again. It passed.
• Checked every package name in every pending .changeset/*.md against all package.json names in the repo. This was the only one missing.
• Reviewed with sol-loop: 1 round with gpt-6.1-sol. Sol verdict: approved.
• Not run locally: the full changeset:version script, which also syncs the Python SDK version and language manifests. Those steps only run once the changesets step succeeds, and the first main run after merge will run them.

Proved by reproducing the CI failure with the same changesets CLI version and watching it pass after the fix.

Model: Claude Opus 5.5 (effort unknown) · Harness: Claude Code in T3 Code

🤖 Generated with Claude Code