Release channels

Signet ships two user-facing release channels:

There is no LTS channel yet. Stable/nightly gives Signet room to move quickly without promising long-term branch support before the project is ready for that maintenance burden.

Policy

Nightly

• Built automatically from main by .github/workflows/release.yml.
• Published to npm with the next dist-tag.
• Created as a GitHub prerelease.
• May include experimental defaults, unstable behavior, and day-to-day development churn.
• Must remain opt-in; Signet should not silently move a stable user to nightly.

Install explicitly:

npm install -g signetai@next

Or switch an existing install’s update checks:

signet update channel nightly

Stable

• Published by manually running .github/workflows/promote-release.yml for a known-good nightly version.
• Promoted to npm latest.
• Marked as a normal GitHub release.
• Default for install and update checks.

Install:

npm install -g signetai

Or switch back from nightly:

signet update channel stable

Update behavior

The daemon stores the user-facing channel in agent.yaml:

updates:
  auto_install: false
  check_interval: 21600
  channel: stable

Compatibility aliases are accepted when reading config or CLI input:

• latest -> stable
• next -> nightly

Channel lookup rules:

• stable checks GitHub latest stable release first, then falls back to npm latest.
• nightly skips GitHub latest and checks npm next directly, so it cannot be accidentally pinned back to stable by the GitHub latest endpoint.

Promotion checklist

Before promoting a nightly to stable:

1. Confirm CI for the nightly release workflow passed.
2. Confirm daemon release assets exist for every supported platform.
3. Confirm the npm package was published under next.
4. Confirm the regression sentinel has not reported a blocker.
5. Run the Promote Release workflow with the exact version.
6. Verify npm latest points to the promoted version:

npm view signetai dist-tags --json