Version Packages (alpha)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@peekdev/cli@0.1.0-alpha.27

Patch Changes

• d18e982: Windows robustness hardening (audit Phase D).

  • peek init's atomic config write now retries the final rename on Windows when
    it hits a transient EBUSY/EPERM/EACCES (the target or temp briefly locked
    by an editor or antivirus), with a short backoff, instead of failing the whole
    init on the first lock. POSIX behaviour is unchanged (single attempt; non-lock
    errors like ENOSPC still fail fast everywhere).
  • The native host now returns a clean error result when persisting a screenshot
    fails (EACCES on ~/.peek, disk full, a Windows lock) instead of throwing —
    which previously skipped the act.response and left the MCP tool call to hang
    until it timed out. The multi-MB base64 is never inlined on the failure path.
  • The stale-bind retry waits a brief beat before rebinding a Windows named pipe
    (released by the OS a moment after the prior host exits), so the single retry
    is more likely to succeed rather than degrading the action write-path.

• Updated dependencies [d18e982]

  • @peekdev/mcp@0.1.0-alpha.21

@peekdev/mcp@0.1.0-alpha.21

Patch Changes

• d18e982: Windows robustness hardening (audit Phase D).
  • peek init's atomic config write now retries the final rename on Windows when
    it hits a transient EBUSY/EPERM/EACCES (the target or temp briefly locked
    by an editor or antivirus), with a short backoff, instead of failing the whole
    init on the first lock. POSIX behaviour is unchanged (single attempt; non-lock
    errors like ENOSPC still fail fast everywhere).
  • The native host now returns a clean error result when persisting a screenshot
    fails (EACCES on ~/.peek, disk full, a Windows lock) instead of throwing —
    which previously skipped the act.response and left the MCP tool call to hang
    until it timed out. The multi-MB base64 is never inlined on the failure path.
  • The stale-bind retry waits a brief beat before rebinding a Windows named pipe
    (released by the OS a moment after the prior host exits), so the single retry
    is more likely to succeed rather than degrading the action write-path.

Summary by CodeRabbit

• Chores
  • Updated CLI package version to 0.1.0-alpha.27
  • Updated MCP package version to 0.1.0-alpha.21

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 43fca49b-bbd8-4ae6-a3fb-2a4a20ee8d1b

📥 Commits

Reviewing files that changed from the base of the PR and between 60af9f5 and b2df7ef.

⛔ Files ignored due to path filters (2)

• packages/peek-cli/CHANGELOG.md is excluded by !**/CHANGELOG.md
• packages/peek-mcp/CHANGELOG.md is excluded by !**/CHANGELOG.md

📒 Files selected for processing (3)

• .changeset/pre.json
• packages/peek-cli/package.json
• packages/peek-mcp/package.json

✅ Files skipped from review due to trivial changes (3)

• packages/peek-cli/package.json
• packages/peek-mcp/package.json
• .changeset/pre.json

---

📝 Walkthrough

Walkthrough

Adds "peek-windows-phase-d-hardening" to the changeset list in .changeset/pre.json, and bumps peek-cli from 0.1.0-alpha.26 to 0.1.0-alpha.27 and peek-mcp from 0.1.0-alpha.20 to 0.1.0-alpha.21.

Changes

Alpha Release Version Bump

Layer / File(s)	Summary
Changeset registration and package version bumps .changeset/pre.json, packages/peek-cli/package.json, packages/peek-mcp/package.json	Registers peek-windows-phase-d-hardening in the pre-release changeset list; increments peek-cli to alpha.27 and peek-mcp to alpha.21.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Cubenest/rrweb-stack#65: Identical release plumbing — updates .changeset/pre.json changeset list and bumps both peek-cli and peek-mcp alpha versions.
• Cubenest/rrweb-stack#81: Same pattern of adding a changeset entry under the alpha pre tag and bumping both package versions.
• Cubenest/rrweb-stack#38: Directly modifies the same changesets array in .changeset/pre.json and bumps the per-package versions.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Version Packages (alpha)' accurately describes the main change: automated version bumps for pre-release packages, which is the primary purpose of this Changesets-generated release PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch changeset-release/main

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}