Repository navigation
Sync release data for server 0.3.0, CLI 0.3.0, edge 0.2.0 - #19
Merged
Merged
Conversation
Regenerated by `node scripts/sync-releases.mjs` after the 0.3.0 releases were published on 2026-10-03. The hourly "Release version check" has failed since then because version.json and the generated pages still listed cli-v0.2.2, v0.2.1 and edge-v0.1.5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
website-mantis | 8341abd | Commit Preview URL Branch Preview URL |
Oct 04 2026, 01:13 AM |
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
2 participants
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.
Why
The hourly Release version check workflow has failed on every run since the 0.3.0 releases were published on 2026-10-03. The job regenerates release data from
privacykey/mantisand fails if the result differs from what is committed. The committed data still listedcli-v0.2.2,v0.2.1andedge-v0.1.5.What
I ran
node scripts/sync-releases.mjsand committed the output. Only generated data changed:version.json: CLIcli-v0.3.0, full serverv0.3.0, edgeedge-v0.2.0404.htmlanden/*.html, plus the structured data on the home pageChecks
node scripts/check.mjspasses (311 local links, 7 themes)node --test tests/*.test.mjspasses (24 of 24)Merging this to
mainalso deploys the site through Cloudflare Workers Builds.🤖 Generated with Claude Code