Skip to content

Releases tab, Notify me and ms_releases (0.4.32) - #44

Merged
MainSequenceDev merged 2 commits into
mainfrom
claude/releases
Nov 19, 2026
Merged

MainSequenceDev merged 2 commits into
mainfrom
claude/releases

Conversation

@MainSequenceDev

@MainSequenceDev MainSequenceDev commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Adds a Releases section and the read-only ms_releases tool (0.4.32). Nothing in it deploys.

Bundles @dev-mainsequence/devtools 0.3.19, locked from the registry (mainsequence-sdk/mainsequence-devtools#31, published).

Releases list:

  • Each row shows the release, its kind, repository · branch, its last ten runs as glyphs, and either "n of m ok" or "Failed/Blocked … ago".
  • What is deploying is pinned on top with commit, stage and elapsed time.
  • Filters: kind, and This repository (the session's checkout); both are applied by the backend.
  • A link opens all deployments, including jobs and images.

A release:

  • The commit and revision it serves, and the one it wants when different.
  • A 7, 30 or 90 day window with success rate, median time, slowest stage and most common failure.
  • Its runs; each run opens the existing deployment detail, and Back returns to the release.

Polling:

  • Nothing is re-read while nothing deploys.
  • While a shown release deploys, one deployment-active check every 30 s. Every session reuses its answer for 25 s through the plugin store.
  • The section is read again only when a shown run ends or one of its releases starts another.
  • It stops with the section, the pane or the session, and pauses after an hour.

Notify me: re-reads one run every 15 s, shows MainSequence: deploying <release> n/m in the status line, and toasts how the run ended.

ms_releases: list, history (release by name or uid), active, and wait (up to 120 s per call; call again while it is still running). It is denied without an environment.

Also fixed: the deployments list's Back always said "← Code". It now names where it returns: Home, Releases or Code.

Verification:

  • MS_CLAUDE_DESKTOP_BINARY=<2.1.325 engine> npm run release:check passes: 147 tests (5 new), engine validation, ZIP inventory and the standalone worker. Run again on the published devtools 0.3.19.
  • The built worker's deployment-releases and deployment-active ran read-only against a real backend: 37 releases in Production, nothing deploying at the time.
  • Not checked in a live Desktop pane yet.

🤖 Generated with Claude Code

MainSequenceDev and others added 2 commits November 18, 2026 20:55
…ys, Notify me and ms_releases

A sixth section lists the environment's APIs, agents and static sites with their last ten
runs, pins what is deploying, and opens a release's serving and wanted commits, 7/30/90
day stats (success rate, median time, slowest stage, most common failure) and runs; a run
opens the existing deployment detail. Read-only: nothing deploys.

Nothing is re-read while nothing deploys. While a shown release deploys, one check every
30 s reads only the queued and running runs, shared by every session for 25 s, and the
section is read again only when a run ends or starts; it stops with the section, the pane
or the session and pauses after an hour. Notify me re-reads one run every 15 s, shows it
in Claude's status line and toasts how it ended.

ms_releases (list, history, active, wait up to 120 s) gives Claude the same read-only view.
The release reads come from devtools 0.3.19. The deployments list's Back now names where
it returns (Home, Releases or Code).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Integrity sha512-EtFXrPsGE8pcfI5uqiSkkKb+vYbfkBbq1exswvajsSKVP7sjCqeYSsjB7X3fxnJLyUz1uemqqXZHXwds2rQxkg== (npm install from the registry).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MainSequenceDev
MainSequenceDev marked this pull request as ready for review November 19, 2026 11:05
@MainSequenceDev
MainSequenceDev merged commit 0f805ad into main Nov 19, 2026
4 checks passed
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