ci: release.py from Tooling at its merged commit #215
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!215
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:ci/tooling-rev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
.tooling-revheld a placeholder since #211, so every release job failed at checkout. It now names Tooling's merged commit withscripts/release.py(Tooling#24,0b0059ac).Testing
Tested: checked that the commit is on Tooling's main and has
scripts/release.py.Still to test: None
Measurements
Nothing to measure: a CI pin.
Risks
A release run is the first real use of the shared
release.py; reverting this commit doesn't help, since the old copy is gone.Checklist
Ready for review
main; the title is a Conventional Commit.mise run testpasses (any failure that also fails onmainis named). Left to CI: no tests run on this PC.main, or Measurements says why there is nothing to measure.third_party/untouched; nothing GPL-incompatible.🤖 Generated with Claude Code
WIP: ci: release.py from Tooling at its merged committo ci: release.py from Tooling at its merged commit