Skip to content

fix(spec,release): Windows-green plan tests + valid release plan#595

Merged
NagyVikt merged 5 commits into
mainfrom
agent/claude/fix-windows-plan-paths-archive-and-relea-2026-06-12-16-11
Jun 12, 2026
Merged

fix(spec,release): Windows-green plan tests + valid release plan#595
NagyVikt merged 5 commits into
mainfrom
agent/claude/fix-windows-plan-paths-archive-and-relea-2026-06-12-16-11

Conversation

@NagyVikt

Copy link
Copy Markdown
Collaborator

Summary

Unblocks CI (Windows) and Release ahead of the version cut:

  • Windows plan tests (the last 3 red tests on main): publishPlan now returns forward-slash spec_change_path/plan_workspace_path (Windows returned backslash absolute paths, failing the contains-assertions), and archiveChange fails deterministically when the archive target exists — POSIX renameSync threw, Windows MoveFileEx silently clobbered, so delta written then archive throws got 'archived' instead of 'error' on Windows.
  • Release workflow crash: the feat(hooks): push contention awareness via PostToolUse additionalContext #594 changeset referenced package colony, which is not a workspace package (the CLI is colonyq) — changesets assemble-release-plan threw on every Release run since. Fixed; pnpm changeset status now assembles cleanly (12 packages at minor).

Test plan

  • pnpm typecheck / pnpm lint / pnpm test (exit 0; spec 19, plan.test.ts green) / pnpm build
  • pnpm changeset status assembles (was: 'Found changeset … for package colony which is not in the workspace')
  • Windows CI jobs on this PR — the actual proof; merging only if all 6 matrix jobs pass

🤖 Generated with Claude Code

NagyVikt added 5 commits June 12, 2026 16:11
…target collision

spec_change_path/plan_workspace_path returned OS-native separators, so
Windows callers (and the plan.test.ts contains-assertions) saw
backslash paths. archiveChange relied on renameSync failing onto an
existing target — POSIX throws, Windows MoveFileEx clobbers — so the
existence check is now explicit.
- publishPlan returns forward-slash spec_change_path/plan_workspace_path
  so Windows callers (and plan.test.ts contains-assertions) see
  separator-stable reference paths.
- archiveChange checks the archive target explicitly: POSIX renameSync
  threw on an existing target, Windows MoveFileEx silently clobbered —
  the 'delta written then archive throws' test now errors on every OS.
- .changeset/post-tool-use-awareness-push.md referenced package 'colony'
  (not in workspace; the CLI is 'colonyq'), which crashed changesets'
  assemble-release-plan and failed every Release run since #594.
…-archived error

mcp-server going green on Windows exposed the next packages in pnpm's
recursive run: 9 apps/cli failures, all path-portability in tests —
expectations assumed POSIX literals where the implementation resolves
and shell-quotes OS-natively. Added shellQuoteForTest mirroring the
production quoting rule; cockpit/queen-health/agents-spawn expectations
now derive from resolve(). PATH stubs join with path.delimiter. The
gx/cue PATH-spawning integration tests gate to POSIX (both tools spawn
via execFileSync without shell, which Windows cannot satisfy).

spec_archive returns structured SPEC_ARCHIVE_ALREADY_EXISTS
(status: already_archived) instead of an opaque throw on same-day
re-archive (review follow-up).
The npm @Colony scope is not ours (@colony/core@3.1.0 belongs to a
different project), so 'changeset publish' would 403 on every public
internal package and fail Release after versioning. colonyq is the
product artifact and ships self-contained (prepack bundles, no
@colony/* deps in the published tarball — e2e-publish green), so the
ten internal packages are now private: publish ships exactly colonyq.
@NagyVikt NagyVikt merged commit 2cc5ff8 into main Jun 12, 2026
15 of 16 checks passed
@NagyVikt NagyVikt deleted the agent/claude/fix-windows-plan-paths-archive-and-relea-2026-06-12-16-11 branch June 12, 2026 15:32
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.

1 participant