Skip to content

Release Aiden Agent 0.60.0 - #578

Merged
sambitcreate merged 2 commits into
mainfrom
claude/project-thread-wrlr9s
Oct 21, 2026
Merged

sambitcreate merged 2 commits into
mainfrom
claude/project-thread-wrlr9s

Conversation

@sambitcreate

@sambitcreate sambitcreate commented Oct 21, 2026 •

Copy link
Copy Markdown
Owner

Requested by sbt · project thread

This bumps package.json and package-lock.json to 0.60.0. Merging it to main runs Release desktop, which publishes v0.60.0.

In this release (since 0.59.0)

Not included: #559 (Bot hand-offs), which is still a draft.

Docs

  • docs/plans/README.md: refreshed for 0.60.0. The MCP, Instant UI and harness rows are marked as shipped.
  • docs/aiden-remote-api-v1.md: "After 0.59.0" now reads "From 0.60.0" for the Bot-chat turn refusal.

Flaky E2E fix

  • Spec: tests/e2e/browser-throttling.spec.ts:14, the first spec in Electron E2E shard 3/3.
  • Symptom: the first attempt failed and the retry passed, so --fail-on-flaky-tests failed the job. The log printed "Downloading Electron binary..." inside the test. The spec then ran into its 60s execFile budget at "starting recording".
  • Run: https://github.com/sambitcreate/aiden-agent/actions/runs/39673903473/job/119488872710
  • Cause: Electron 43 resolves its binary lazily. On a fresh shard, the first spec paid for the binary download and the first-launch signature check inside its own budget.
  • Fix: a Playwright globalSetup (tests/e2e/global-setup.ts) resolves the binary and runs electron --version once before any spec. No timeouts or retries changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SE574SfMr5QCRmoYLXy2D7

Bump package.json and package-lock.json so the Release desktop workflow
publishes v0.60.0, and record the MCP move to pi-mcp (#568), Instant UI
(#576) and the harness reliability foundation (#553 via #577) as shipping
in 0.60.0 in the plan index.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SE574SfMr5QCRmoYLXy2D7
@sambitcreate sambitcreate self-assigned this Oct 21, 2026

@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 Reviewed the complete release-version and documentation diff, including its interaction with the existing desktop release workflow.

  • Release identity: package.json and both root lockfile version fields consistently advance to 0.60.0; the release selector produces v0.60.0 with publication enabled when that tag is absent.
  • Release documentation: The plan inventory records the merged release contents and outstanding acceptance gates, and the Remote API guide identifies 0.60.0 as the version introducing the existing legacy Bot-turn refusal.
  • Validation: All 29 focused release-selection, consumer-contract, publishing, Linux-feed, and CI-policy tests passed. Hosted CI is still running; signed distribution and macOS/Electron acceptance were not run locally on this Linux runner.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@very-hermes-bot

very-hermes-bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Hermes Review Bot

Confidence: 5

Engine: agy/gemini-3.8-flash-high
Review mode: full
Head: 3ad7fd3dee2d18d93910d697c950d1d8cf1ba5b1
Generated: 2026-10-21T21:51:30+00:00
Reviews: 1

Summary

Bumps the application version in package.json and package-lock.json from 0.59.0 to 0.60.0 for the desktop release workflow, and updates plan milestones and Remote API documentation to match. It also introduces a Playwright globalSetup hook that invokes the Electron binary with --version once before any specs run, preventing cold-start macOS Gatekeeper signature verification latency on fresh CI shards from exhausting individual test timeouts. Maintainers should double-check that all required CI matrix checks complete cleanly on the head commit prior to merging into main to trigger the automated release build.

Confidence Score: 5/5

5/5: Diff, git history, documentation claims, CI workflows, and the Playwright global setup hook were thoroughly inspected and verified against existing codebase conventions.

📁 Important Files Changed

Findings

No findings.

📊 Sequence Diagram

Unchanged or not applicable for this change.

Machine-Readable Findings

[]

Last reviewed commit: 3ad7fd3dee2d
Reviews (1) · Comment /hermes review to trigger a new review · /hermes review full for full re-review

Electron resolves its binary lazily, so on a fresh CI shard the first spec
downloaded it and then paid the first-launch signature check inside its own
60s budget. browser-throttling.spec.ts runs first in shard 3 and failed its
first attempt that way on the 0.60.0 release PR (passed on retry, which
--fail-on-flaky-tests rejects). A Playwright global setup now resolves and
starts the binary once before any spec.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SE574SfMr5QCRmoYLXy2D7

@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 Reviewed the Electron E2E setup changes since the prior review at 4938095, with the complete release diff as context.

  • Added suite-level warm-up: Registered a global setup that resolves Electron before the specs and attempts a bounded --version launch, moving lazy binary installation and first-launch work outside individual test budgets.
  • Preserved test enforcement: Left spec timeouts, retries, and --fail-on-flaky-tests unchanged; warm-up launch failures remain the specs' responsibility.
  • Validated configuration: E2E type-checking passed, Playwright collected 223 tests in 42 files, and all 21 focused sharding and CI-policy tests passed. Direct setup invocation completed on Linux, but macOS first-launch behavior and the original flake remain unverified locally. Exact-head hosted CI was still running.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@sambitcreate
sambitcreate merged commit 69b4b85 into main Oct 21, 2026
27 checks passed
@sambitcreate
sambitcreate deleted the claude/project-thread-wrlr9s branch October 21, 2026 22:17
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.

3 participants