Skip to content

chore(cli): pin core 15.0.7 #2048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kjgbot merged 2 commits into from
Nov 1, 2026
Merged

chore(cli): pin core 15.0.7 #2048

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dca2952
chore(cli): pin core 15.0.7 and fix the npx hints changelog entry
Nov 1, 2026
b496c6b
docs(changelog): state what relay init prints under npx
Nov 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Fixed

- With the desktop app on the machine, `relay init --hosted` and `relay workspace create` use `https://cast.agentrelay.com`, the only server its core serves, and `relay init --key` refuses an armadillo key instead of saving a workspace agents could not join.
- `relay init` run through `npx` prints follow-up commands that also use `npx`, so they work without a global `relay` install.

## [15.0.0] - 2026-10-31

Expand Down Expand Up @@ -49,7 +50,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Fixed

- `relay init` run through `npx` prints follow-up commands that work there, because `relay` is not on PATH after `npx`.
- Grok CLI sessions now join Relay after `relay init`. The core refused every open Grok session with "A signed-in owner is required for managed sessions." because release builds never attach a Cloud install; a Grok session now belongs to the signed-in account, or to this computer's OS user when nobody is signed in.
- Broker: `spawn:<harness>` capabilities now declare `metadata.configured.node_kind: "broker"`, so Cloud keeps placing spawns on unclaimed CLI brokers instead of refusing them until `agent-relay node claim`. An already-declared kind (e.g. `desktop`) is preserved.
- `relay init` downloads the standalone Relaycast server (`relaycast-engine`) for your platform into the install directory's `bin` when it is missing, verifying its SHA-256, so the local server now starts from an npm install on any Node.js version and with npm install scripts disabled. It falls back to the `@relaycast/engine` npm package only if the download fails.
Expand Down
2 changes: 1 addition & 1 deletion packages/cli/src/cli/lib/probe-core.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ import type { EnginePlatform } from './relaycast-engine-install.js';
import { relaySkillRecordOf, type RelaySkillRecord } from './relay-skill.js';

/** The core `relay init` installs. Pinned so every machine runs the same core. */
export const PROBE_VERSION = '15.0.6';
export const PROBE_VERSION = '15.0.7';
/** Release tags of the core; distinct from the CLI's `v*` tags. */
export const PROBE_TAG_PREFIX = 'probe-v';
const RELEASE_BASE = 'https://github.com/AgentWorkforce/relay/releases/download';
Expand Down
Loading