5 Commits
edge ... v1.0.1

Author SHA1 Message Date
53e32a0ba4 Merge pull request 'chore(release): RunicNPC cutover for the 2026-11-05 wipe, Rust 547616323393184824' (#29) from edge into main
All checks were successful
Release plugin / release (push) Successful in 28s
Wipe-day cutover / cutover (push) Successful in 12s
Staging drill / drill (push) Successful in 24s
2026-11-06 14:13:36 +00:00
27ff34e689 Merge pull request 'ci(cutover): main's cutover.yml is edge's again, so the cutover PR merges (D397)' (#30) from ci/cutover-yml-match-edge into main
All checks were successful
Release plugin / release (push) Successful in 8s
Wipe-day cutover / cutover (push) Successful in 32m49s
Reviewed-on: #30
2026-11-06 13:26:05 +00:00
8a9e8fa4b1 ci(cutover): main's cutover.yml is edge's again, so the cutover PR merges (D397)
All checks were successful
PR Checks / plugin-checks (pull_request) Successful in 21s
runicnpc-rust#28 changed edge's copy of cutover.yml (gate 1 reads Steam; the
staging static half is gone). main's copy was added by its own commit (#26), so
the two now conflict (add/add) and the cutover PR #29 cannot merge, though all
its gates passed. This makes main's copy byte-for-byte edge's. It changes no
commit on edge, so the gates kept for edge 761a9b67 stand and the next hourly
run only re-checks the PR and merges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014HJEmgsXtLR5kLfh7f9y8P
2026-11-06 06:59:53 -06:00
c57456264d Merge pull request 'ci(cutover): the wipe-day cutover's trigger on main (D332)' (#26) from ci/cutover-trigger into main
Some checks failed
Release plugin / release (push) Successful in 10s
Staging drill / drill (push) Successful in 9s
Wipe-day cutover / cutover (push) Failing after 2m46s
Reviewed-on: #26
2026-11-02 15:39:01 +00:00
567b7671ad ci(cutover): the wipe-day cutover's trigger on main (D332)
All checks were successful
PR Checks / plugin-checks (pull_request) Successful in 11s
Gitea fires a schedule only from the default branch, so the cutover's
workflow file reaches main once, alone. It is the same file as on edge
(the trigger and the step wiring); every step checks out edge and runs
edge's scripts, so nothing else of edge comes with it: the field list stays
on edge until the cutover merges it. A ci: commit cuts no release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
2026-11-02 07:09:11 -06:00

Diff Content Not Available