ci(rust): pin core to main at the cutover (website#220) #57

wtclaude · 2026-10-22T05:45:40-05:00

wtclaude commented

2026-10-22 05:45:40 -05:00

What & why

Step 2 of PLAN_LAST_FIXES stage 6. website#220 cut website edge over to main as 6890a74. ci/core-ref.json
pointed at 9a1654f (website#218's merge into edge), and its own note said it moves to main when the cutover lands.

The new tree adds the last fixes' core half (website#219, no MODULE_API bump). Its only route changes are core's own
event routes, so routes.manifest.json does not change. One file changes: ci/core-ref.json.

After this merges, I open Module-Rust edge → main. The Rust bundle it needs is already out:
v2/rust/current.json is 2026.10.22, protocol 14, Rust-Link v0.3.0, Rust-Plugins v0.3.0 and RunicNPC v1.0.0,
composed by compose run 201. Each hash in it matches its release's SHA256SUMS.

How it was tested

I replayed the frozen-manifest job locally at 6890a74, with the same steps as the CI job. Core's own manifest
--check is current (281 routes), the module registers, and frozenManifest.js --check passes (89 routes, all
documented). This PR's checks run the same job.

Checklist

I have read CONTRIBUTING.md.
The change builds and existing tests/checks pass locally.
I have added or updated tests/docs where it makes sense.
My commits are reasonably scoped with clear messages.

AI-assisted contributions (required)

No AI tools were used to produce this contribution.
AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). I have reviewed and understand every change, and
take responsibility for it. AI-authored commits are marked with a Co-Authored-By trailer.

License

I agree that my contribution is licensed under this project's license (GNU GPL v3.0 or later), and I have
the right to contribute it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why Step 2 of PLAN_LAST_FIXES stage 6. website#220 cut website `edge` over to `main` as `6890a74`. `ci/core-ref.json` pointed at `9a1654f` (website#218's merge into `edge`), and its own note said it moves to `main` when the cutover lands. The new tree adds the last fixes' core half (website#219, no MODULE_API bump). Its only route changes are core's own event routes, so `routes.manifest.json` does not change. One file changes: `ci/core-ref.json`. **After this merges**, I open Module-Rust `edge` → `main`. The Rust bundle it needs is already out: `v2/rust/current.json` is **2026.10.22**, protocol 14, Rust-Link v0.3.0, Rust-Plugins v0.3.0 and RunicNPC v1.0.0, composed by compose run 201. Each hash in it matches its release's `SHA256SUMS`. ## How it was tested I replayed the frozen-manifest job locally at `6890a74`, with the same steps as the CI job. Core's own manifest `--check` is current (281 routes), the module registers, and `frozenManifest.js --check` passes (89 routes, all documented). This PR's checks run the same job. ## Checklist - [x] I have read CONTRIBUTING.md. - [x] The change builds and existing tests/checks pass locally. - [x] I have added or updated tests/docs where it makes sense. - [x] My commits are reasonably scoped with clear messages. ## AI-assisted contributions (required) - [ ] No AI tools were used to produce this contribution. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with a `Co-Authored-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**), and I have the right to contribute it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-10-22 05:45:42 -05:00

ci(rust): pin core to main at the cutover (website#220)

PR Checks / client-build (pull_request) Successful in 31s

Details

PR Checks / frozen-manifest (pull_request) Successful in 59s

Details

PR Checks / server-tests (pull_request) Successful in 7m15s

Details

3453bc1867

website#220 cut website edge over to main as 6890a74. The pin pointed at
9a1654f, the sha website#218 merged into edge as, which its own note said
moves to main when the cutover lands. The new tree adds the last fixes'
core half (website#219, no MODULE_API bump), whose route changes are only
core's own event routes, so routes.manifest.json does not change. The
frozen-manifest job, replayed locally at this ref, passes (89 routes, all
documented).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit 42bd6db6ad into edge

2026-10-22 06:13:59 -05:00

whitlocktech deleted branch chore/pin-core-main

2026-10-22 06:14:00 -05:00

whitlocktech referenced this issue from a commit

2026-10-22 06:14:01 -05:00

Merge pull request 'ci(rust): pin core to main at the cutover (website#220)' (#57) from chore/pin-core-main into edge

wtclaude referenced this pull request

2026-10-22 06:14:56 -05:00

chore(release): cut edge over to main — protocol 14 and Steam sign-in (MODULE_API 1.17.0) #58

Sign in to join this conversation.