chore(agents): /release, a skill that tags an rc or a stable and writes the release page's What's new #742

Merged

HumanBean merged 1 commit from HumanBean/Longshot:chore/release-skill into main 2026-11-15 09:08:00 +00:00

Conversation 0 Commits 1 Files changed 1 +90

HumanBean commented 2026-11-15 08:56:04 +00:00

Owner

• Copy link
• Copy Markdown

Type: chore · Risk: low · Tested on: Linux (cut the launcher's v1.0.0-rc.6 with it) · Needs: none

Why

Cutting a release is several steps from RELEASING.md, and CI writes only git-cliff's notes, so the player-friendly "What's new" at the top of a release page (v3.0.0-rc.4) is written by hand each time. A /release skill lets an agent do all of it the same way every time.

What changed

/release rc or /release stable follows RELEASING.md: it tags the next rc on main (or the tested rc's commit as stable), checks the tag with release.py check-tag and pushes it. Then it waits for CI and writes the summary between the downloads' --- and the version's heading.

• Before an rc (Longshot only), it asks which of RELEASING's pre-release refreshes to do first, each a PR merged before the tag: the pipeline tour with the renderer's play profile (one run, --vk-profile), and the build times (docs/development.md).
• .claude/skills/release/SKILL.md: the skill. It is the same file in LongshotLauncher (like RELEASING.md), and finds the MagicBeanDev/* remote itself.
• The summary copies each repository's earlier ones: Longshot's v3.0.0-rc.4 (bold themes with the measured numbers, New:, Fixed:, its own ---), the launcher's v1.0.0-rc.4 (bold-led bullets, Fixes:).
• It signs in through scripts/forge.py (import forge, forge.api), never touching the token, and edits only the body: CI's last step sets only draft and prerelease, so the summary survives the publish.

Measurements

Verdict: nothing to measure: a Markdown file for agents, no code.

Flags and settings

None

Testing

Tested: cut the launcher's v1.0.0-rc.6 with these steps (tag, check-tag, push, CI on the release runner, the summary patched in through forge.api): https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/releases/tag/v1.0.0-rc.6. python -I -B tests/run_all.py: 509 passed, 14 failed, 70 skipped. The 14 (test_make_game_cache, test_lift_cleanup_error, test_bake_portability, test_crash_dialog, test_cpm_discovery, test_env_on, test_appimage_player_build, test_linux_preflight, test_options_budget_once, test_pipeline_tour, test_mods_size_table, test_readback_late, test_vk_pgo, test_walk_key) fail on main too: this branch is main plus one Markdown file.

Not tested: a Longshot release with it (the next one will be the first).

Must be tested: None

Risks

What could break: nothing in the game or the builder. A wrong skill step could tag a wrong commit; the skill runs check-tag before pushing, as CI does.

Turning it off: revert the commit

Compatibility: Nothing changes

Checklist

Everyone

• One topic.
• The title is a Conventional Commit (type(scope): description) of the status line's type.
• Why gives the reason plainly and links the issues that fit (the tracker searched).
• Measurements has a verdict, or one line saying why there is nothing to measure.
• Testing names what was tested, what wasn't, and what must still be tested, where and how.
• Rebased on current main.
• python -I -B tests/run_all.py passes (any failure that also fails on main is named).
• No game files, dumps, build output or generated files.
• third_party/ untouched (a new folder with a PROVENANCE.md instead).
• The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

• AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
• Docs updated.

🤖 Generated with Claude Code

**Type:** chore · **Risk:** low · **Tested on:** Linux (cut the launcher's v1.0.0-rc.6 with it) · **Needs:** none ## Why Cutting a release is several steps from RELEASING.md, and CI writes only git-cliff's notes, so the player-friendly "What's new" at the top of a release page (v3.0.0-rc.4) is written by hand each time. A `/release` skill lets an agent do all of it the same way every time. ## What changed `/release rc` or `/release stable` follows RELEASING.md: it tags the next rc on `main` (or the tested rc's commit as stable), checks the tag with `release.py check-tag` and pushes it. Then it waits for CI and writes the summary between the downloads' `---` and the version's heading. - Before an rc (Longshot only), it asks which of RELEASING's pre-release refreshes to do first, each a PR merged before the tag: the pipeline tour with the renderer's play profile (one run, `--vk-profile`), and the build times (docs/development.md). - `.claude/skills/release/SKILL.md`: the skill. It is the same file in LongshotLauncher (like RELEASING.md), and finds the `MagicBeanDev/*` remote itself. - The summary copies each repository's earlier ones: Longshot's v3.0.0-rc.4 (bold themes with the measured numbers, **New:**, **Fixed:**, its own `---`), the launcher's v1.0.0-rc.4 (bold-led bullets, **Fixes:**). - It signs in through `scripts/forge.py` (`import forge`, `forge.api`), never touching the token, and edits only the body: CI's last step sets only `draft` and `prerelease`, so the summary survives the publish. ## Measurements **Verdict:** nothing to measure: a Markdown file for agents, no code. ### Flags and settings None ## Testing **Tested:** cut the launcher's `v1.0.0-rc.6` with these steps (tag, `check-tag`, push, CI on the release runner, the summary patched in through `forge.api`): https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/releases/tag/v1.0.0-rc.6. `python -I -B tests/run_all.py`: 509 passed, 14 failed, 70 skipped. The 14 (test_make_game_cache, test_lift_cleanup_error, test_bake_portability, test_crash_dialog, test_cpm_discovery, test_env_on, test_appimage_player_build, test_linux_preflight, test_options_budget_once, test_pipeline_tour, test_mods_size_table, test_readback_late, test_vk_pgo, test_walk_key) fail on `main` too: this branch is `main` plus one Markdown file. **Not tested:** a Longshot release with it (the next one will be the first). **Must be tested:** None ## Risks **What could break:** nothing in the game or the builder. A wrong skill step could tag a wrong commit; the skill runs `check-tag` before pushing, as CI does. **Turning it off:** revert the commit **Compatibility:** Nothing changes ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

HumanBean added 1 commit 2026-11-15 08:56:05 +00:00

chore(agents): /release, a skill that tags an rc or a stable and writes the release page's What's new ... 08f2e7ed3d

Co-Authored-By: Claude Opus 5.5 <[email protected]>

HumanBean referenced this pull request from MagicBeanDev/LongshotLauncher 2026-11-15 08:56:14 +00:00

chore(agents): /release, a skill that tags an rc or a stable and writes the release page's What's new #91

HumanBean force-pushed chore/release-skill from 08f2e7ed3d to 5ae8ff2f24 2026-11-15 09:06:32 +00:00 Compare

HumanBean force-pushed chore/release-skill from 5ae8ff2f24 to f3ddf7225b 2026-11-15 09:06:45 +00:00 Compare

HumanBean referenced this pull request from a commit 2026-11-15 09:07:56 +00:00

chore(agents): /release, a skill that tags an rc or a stable and writes the release page's What's new (#91)

HumanBean merged commit a00c485c71 into main 2026-11-15 09:08:00 +00:00

HumanBean deleted branch chore/release-skill 2026-11-15 09:08:00 +00:00

HumanBean referenced this pull request from a commit 2026-11-15 09:08:01 +00:00

chore(agents): /release, a skill that tags an rc or a stable and writes the release page's What's new (#742)

nyannoying referenced this pull request 2026-11-15 10:18:07 +00:00

perf(vk): Arc cards read the occlusion counts from a GPU copy: Castle Town's market from 34.8 to 45.8 fps on a B580 #761

HumanBean referenced this pull request from a commit 2026-11-15 10:22:55 +00:00

perf(vk): Arc cards read the occlusion counts from a GPU copy: Castle Town's market from 34.8 to 45.8 fps on a B580 (#761)

GrimVisage referenced this pull request 2026-11-15 10:54:02 +00:00

docs(tested): Threaded rendering (#588) in the Market on a 6-core Linux desktop, interleaved Off and Auto #688

zeldaootr referenced this pull request 2026-11-15 16:41:51 +00:00

fix(vk): a mesh fallback program with bigger payloads reuses the record arena #551

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

area/accessibility

Barriers for people with disabilities

  

area/audio

Sound and music

  

area/input

Controllers, keyboard, mouse

  

area/install

Installing, updating, building from your game

  

area/menu

In-game menu and settings

  

area/renderer

Vulkan renderer, shaders, effects

  

area/saves

Save files

  

area/tooling

Developer tools: scripts, CI, build and release tooling

  

area/upscaling

DLSS, FSR, frame generation

  

ci: approved

A maintainer approved CircleCI for this fork PR (sticky; removed after 14 quiet days)

  

good first issue

A good start for a new contributor

  

gpu/amd

AMD GPUs

  

gpu/igpu

Integrated GPUs

  

gpu/intel

Intel GPUs

  

gpu/nvidia

NVIDIA GPUs

  

help wanted

Extra hands or knowledge wanted

  

kind

bug

Something doesn't work as it should

  

kind

chore

Build, CI, dependencies, tidying

  

kind

docs

Documentation

  

kind

feature

A new feature or an improvement

  

kind

performance

Frame rate, frame time, loading, memory

  

kind

question

A question rather than a change

  

needs measurements

Waiting for before/after measurements

  

platform/linux

Affects Linux (a change for every system carries both Windows and Linux)

  

platform/macos

macOS (Apple silicon or Intel Macs)

  

platform/steam-deck

Steam Deck

  

platform/windows

Affects Windows (a change for every system carries both Windows and Linux)

  

preview

Maintainers: deploy a preview of this PR's website (read its changes first). Removed after the run.

  

priority

critical

Crashes, data loss, or blocks most players

  

priority

high

Important: next in line

  

priority

low

Nice to have

  

regression

Worked in an earlier build, broken in a newer one: highest priority, above other bugs

  

risk

high

Broad or core change: the renderer, defaults on many systems, saves, installs, security

  

risk

low

Small, contained change: little can break

  

risk

medium

Changes behaviour in one area, or a default on some systems

  

status

blocked

Waits on something else first

  

status

confirmed

Reproduced or agreed on

  

status

duplicate

Already reported or proposed

  

status

invalid

Not a problem in this project

  

status

needs-info

Waiting for more information from the reporter

  

status

wontfix

Will not be worked on

  

testing wanted

Wanted: a test on other hardware (posts a test request in #test-requests)

  

ci: approved

No labels

area/accessibility

area/audio

area/input

area/install

area/menu

area/renderer

area/saves

area/tooling

area/upscaling

ci: approved

good first issue

gpu/amd

gpu/igpu

gpu/intel

gpu/nvidia

help wanted

kind

bug

kind

chore

kind

docs

kind

feature

kind

performance

kind

question

needs measurements

platform/linux

platform/macos

platform/steam-deck

platform/windows

preview

priority

critical

priority

high

priority

low

regression

risk

high

risk

low

risk

medium

status

blocked

status

confirmed

status

duplicate

status

invalid

status

needs-info

status

wontfix

testing wanted

ci: approved

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

MagicBeanDev/Longshot!742

No description provided.