Repository navigation
chore: prepare Swarmail 0.8.0 - #222
Merged
Merged
Conversation
Set the version to 0.8.0 in package.json, packages/mcp-relay/package.json and both server.json fields, and date the changelog section. The changelog audit merged the two lifecycle-check entries, removed a transient CPU figure, added that an existing swarmail MCP entry is now left as it is, and states which T3 Code versions the comparison covers. docs/provider-coverage.md says stable 0.1.4 and 0.1.5 were not checked.
Owner
Author
|
@coderabbitai full review |
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.
Prepares release 0.8.0: the version is 0.8.0 in
package.json,packages/mcp-relay/package.jsonand both fields inserver.json, and the changelog section is headed0.8.0 - 2026-10-30. Merging this does not tag or publish anything.Changelog audit (each entry checked against the code that ships, not copied):
data_versiongate) are one entry that states the final behavior; the copy-server CPU figure is removed because it came from one harness and did not combine across the two changes.swarmailentry that had the managed URL, and feat: configure selected MCP clients [skip review] #212 leaves it alone. The entry now says so.docs/provider-coverage.mdsays the same.git log v0.7.2..HEAD: docs: add the compact MCPRush badge #210, docs: account for T3 linked-machine orchestration #211, feat: configure selected MCP clients [skip review] #212, perf: read only the lifecycle payload fields the check uses #216, fix: keep self names inside the project the guard checks #217, perf: skip unchanged lifecycle reads with SQLite data_version #219, ci: publish releases from a GitHub Actions workflow on a version tag #221. The rest (docs: record the MCP client selection in the changelog #213, docs: list the mcpservers.org submission in CONTRIBUTING #214, ci: remove the shadow review workflow; the bompus-ai-review GitHub App reviews this repository #215, Bump oxfmt to 0.75.0 and oxlint to 1.90.0 #220) change documentation, CI or development tools only.Accuracy audit of public materials, no change needed:
README.mdandpackages/mcp-relay/README.mdchanged since 0.7.2 only by the MCPRush badge (badge image returns 200); no sentence names a version that this release makes stale (the benchmark notes say "0.2.0 or any later release").server.jsonandpackage.jsondescriptions passcheck-release; the repository description, homepage (the npm page ofswarmail-mcp), topics and custom social preview are unchanged and no banner or preview text changed.docs/usage.mdand the graphics did not change, soevals/docs-checkwas not rerun.Checks:
bun run checkpasses. The fullbun testrun had 1 to 2 failures that differ between runs:two concurrent first edits of one session register oncealso fails on unmodifiedmain(1 pass, 1 fail in two isolated runs), and a wake-auto-t3 ordering test failed once under load and passed alone. Neither touches this diff; CI is the record for this head.Release notes the workflow will use are the
0.8.0section ofCHANGELOG.md, extracted verbatim.