Version Packages - #225
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
August 27, 2026 15:00
4f44b59 to
de2598c
Compare
winsznx
added a commit
that referenced
this pull request
Aug 30, 2026
PR #255 rewrote release.yml to add a failure watchdog and dropped most of the working config in the process. That is on me — I merged it in a batch without reading the diff closely enough. What it removed: - `contents: write` and `pull-requests: write`, reduced to `issues: write`. Those are what let Changesets commit the version bump and open the release PR, and restoring them is what fixed #208 in the first place. - The pnpm 9.15.9 and Node 22 pins, leaving the job on corepack defaults and undoing part of #214. - `GITHUB_TOKEN` and `NPM_TOKEN` on the changesets action. And the watchdog it added called `gh` with no `GH_TOKEN`, so the step failed on every run: gh: To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN ##[error]Process completed with exit code 4 Net effect: Release has been red on every push since, and #225 has been stuck three changesets behind while main accumulated seven — Changesets could not update it without pull-requests: write. The watchdog meant to surface release failures was the thing causing them. Restores the known-good config, keeps issues: write, and reworks the watchdog to pass GH_TOKEN and deduplicate so a run of red pushes files one issue instead of one per commit.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 30, 2026 18:49
de2598c to
4d5fe7d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 30, 2026 19:43
4d5fe7d to
211a8a2
Compare
winsznx
pushed a commit
that referenced
this pull request
Aug 30, 2026
.github/workflows/*.yml was the only code in the repo with no automated checking. PR #255 removed contents: write and pull-requests: write from release.yml in the same rewrite that added a watchdog calling gh with no GH_TOKEN set -- every Release run failed until #225 caught up three changesets late. A linter would have caught the missing GH_TOKEN outright. Add actionlint as a CI job, plus a narrow guard asserting release.yml still declares contents: write and pull-requests: write, since that specific regression has now cost two outages. Closes #264
github-actions
Bot
force-pushed
the
changeset-release/main
branch
14 times, most recently
from
August 31, 2026 10:44
07c4d2f to
28413dc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 31, 2026 10:45
28413dc to
f31c087
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 31, 2026 15:54
f31c087 to
729b404
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
Releases
@routedock/mcp-server@0.2.0
Minor Changes
4da4b78Thanks @Jaydearcadian! - Restore the public npm release pipeline, build every publishable package before publication, and prepare the RouteDock packages for their 0.2.0 releases.Patch Changes
4da4b78,e0eea65,d9ac7f4,5c6b01f,e571dd4,2eac983,291afa5,d291a14]:@routedock/nulth-sdk@0.2.0
Minor Changes
4da4b78Thanks @Jaydearcadian! - Restore the public npm release pipeline, build every publishable package before publication, and prepare the RouteDock packages for their 0.2.0 releases.Patch Changes
2eac983Thanks @TS-mfon! - Block the insecure Nulth mock prover on mainnet and stop advertising an unimplemented WASM backend.@routedock/routedock@0.2.0
Minor Changes
#180
4da4b78Thanks @Jaydearcadian! - Restore the public npm release pipeline, build every publishable package before publication, and prepare the RouteDock packages for their 0.2.0 releases.#181
e0eea65Thanks @Jaydearcadian! - Enforce manifest and payment-mode deprecation, reject sunset manifests including cached entries, and expose per-endpoint deprecation metadata.#240
5c6b01fThanks @chiomailekuba! - Secure manifest signatures with versioned recursive canonicalization so nested pricing, endpoint, channel, SLA, and capability fields cannot be modified without invalidating the signature.#231
291afa5Thanks @melanindebbie! - RespectCache-Control: max-age/Expiresresponse headers for per-entry manifest cache TTL, and exposeRouteDockClient.invalidateManifest(url)for explicit eviction so provider manifest updates take effect before the default TTL expires.#227
d291a14Thanks @melanindebbie! - Addmpp-session-ws: a WebSocket transport variant ofmpp-sessionthat opens the channel, negotiates the voucher over HTTP, then upgrades the connection to WebSocket for push-based streaming from inference providers. Includes Hono provider support (shared channel store across both session transports), manifest schema, and mode selection via atransport: 'websocket'option.Patch Changes
#241
d9ac7f4Thanks @chiomailekuba! - Preserve typed Stellar MPP channel verification failures and make provider-side channel envelope authorization explicit during close and recovery operations.#260
e571dd4Thanks @Olalolo22! - Add registerProvider helper to verify manifest signature and upsert into Supabase provider registry on startup.#237
2eac983Thanks @TS-mfon! - Block the insecure Nulth mock prover on mainnet and stop advertising an unimplemented WASM backend.Updated dependencies [
4da4b78,2eac983]: