Skip to content

chore(deps): bump @relayfile/sdk ^0.8.16 → ^0.8.20 (activates #184 mount-optional-dep)#190

Merged
khaliqgant merged 1 commit into
mainfrom
chore/bump-relayfile-sdk-0.8.20
Jun 9, 2026
Merged

chore(deps): bump @relayfile/sdk ^0.8.16 → ^0.8.20 (activates #184 mount-optional-dep)#190
khaliqgant merged 1 commit into
mainfrom
chore/bump-relayfile-sdk-0.8.20

Conversation

@khaliqgant

Copy link
Copy Markdown
Member

What

Bumps @relayfile/sdk ^0.8.16^0.8.20 + relocks package-lock.json.

Why

@relayfile/sdk@0.8.20 declares the platform mount binary as optional dependencies (@relayfile/mount-{darwin,linux}-{arm64,x64}@0.8.20). Relocking pulls those into the lockfile, so the #184 launcher (src/main/relayfile-mount-launcher.ts) resolves relayfile-mount from the npm optional package — no postinstall download. This is the activation step for the already-merged #184 (dc80afb); without the sdk bump the lockfile still pinned 0.8.16 (no mount-* optional deps).

The mount binary is now v0.8.20 = the relayfile#264 durable-outbox + --flush-outbox-once build (the same cure now live on the cloud fleet).

Verification

🤖 Generated with Claude Code

…ount-optional-dep

@relayfile/sdk@0.8.20 declares the @relayfile/mount-{darwin,linux}-{arm64,x64}@0.8.20 optional deps, so relocking pulls the platform mount binary as an npm optional package (no postinstall download) — activating the #184 launcher resolution (relayfile-mount-launcher.ts). All four mount-*@0.8.20 verified published on npm.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@codeant-ai

codeant-ai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI.

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The @relayfile/sdk dependency version constraint in package.json was updated from ^0.8.16 to ^0.8.20, enabling the project to pull newer patch releases of the SDK within the same minor version range.

Changes

Dependency Update

Layer / File(s) Summary
@relayfile/sdk version constraint update
package.json
@relayfile/sdk dependency bumped from ^0.8.16 to ^0.8.20 in dependencies to capture newer patch releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump, so small and neat,
From point-one-six to point-two-oh complete,
The SDK grows, the constraints stay,
A simple hop to a brighter day!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: bumping @relayfile/sdk from ^0.8.16 to ^0.8.20 and activating the mount-optional-dep feature from PR #184.
Description check ✅ Passed The description is well-detailed and directly related to the changeset, explaining both what changed (SDK version bump and lockfile relock) and why (activates optional dependency mount packages).
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 chore/bump-relayfile-sdk-0.8.20

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
package.json (1)

36-36: Validate @relayfile/sdk version bump to ^0.8.20

  • @relayfile/sdk@0.8.20 exists on npm.
  • No known security advisories were returned for @relayfile/sdk (via the GitHub security advisories query).
  • Skim the @relayfile/sdk 0.8.20 release notes/changelog to confirm no behavioral changes affect the mount-optional-dep activation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 36, Verify the `@relayfile/sdk` version bump to ^0.8.20
by confirming the package exists on npm and reviewing the 0.8.20 release
notes/changelog for any behavioral or breaking changes that could affect our
mount-optional-dep activation; specifically search the changelog and commit diff
for mentions of "mount-optional-dep", activation logic, initialization APIs, or
config keys used by our code, then run unit and integration tests and a local
scenario that exercises the mount-optional-dep activation path (the code paths
that check/enable mount-optional-dep) to ensure no runtime changes are required.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@package.json`:
- Line 36: Verify the `@relayfile/sdk` version bump to ^0.8.20 by confirming the
package exists on npm and reviewing the 0.8.20 release notes/changelog for any
behavioral or breaking changes that could affect our mount-optional-dep
activation; specifically search the changelog and commit diff for mentions of
"mount-optional-dep", activation logic, initialization APIs, or config keys used
by our code, then run unit and integration tests and a local scenario that
exercises the mount-optional-dep activation path (the code paths that
check/enable mount-optional-dep) to ensure no runtime changes are required.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2536a2d-0adb-4e8d-b6f9-ef8dd96b588b

📥 Commits

Reviewing files that changed from the base of the PR and between 7092a37 and d6f2d3a.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

@khaliqgant khaliqgant merged commit 0a30e1f into main Jun 9, 2026
4 checks passed
@khaliqgant khaliqgant deleted the chore/bump-relayfile-sdk-0.8.20 branch June 9, 2026 20:47
@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

1 similar comment
@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

@agent-relay-code

Copy link
Copy Markdown
Contributor

ℹ️ pr-reviewer: review only — no file changes were applied to the PR (nothing to commit after review). The notes below are advisory and were not pushed.

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer could not complete review for #190 in AgentWorkforce/pear.
The review harness exited with code 1.
No review was posted; this needs operator attention.

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