Tags: cv/kananeko
Tags
ci: release every commit in a push Change the ROM release workflow from a single-ref build into a two-stage flow: a collector job resolves the exact commit SHAs to build, and the release job runs as a matrix over every commit in that set. On normal pushes to main this means every commit in the pushed range gets its own ROM prerelease, not just the tip commit. For manual backfills, workflow_dispatch now accepts either a single ref or a git revision range, so historical releases can be queued from the GitHub UI without keeping a separate helper script in the repository. Delete scripts/backfill-rom-releases.sh since the workflow itself now owns that backfill behavior.
ci: pin release builds to node 25.9 The historical backfill run showed that many older commits predate .nvmrc, so actions/setup-node failed before the build even started. Pin the release workflow to Node 25.9.0 directly instead of reading the version from the checked-out commit. That keeps current builds on the same runtime we use locally while also letting old commits build successfully during workflow_dispatch range backfills.
ci: pin release builds to node 25.9 The historical backfill run showed that many older commits predate .nvmrc, so actions/setup-node failed before the build even started. Pin the release workflow to Node 25.9.0 directly instead of reading the version from the checked-out commit. That keeps current builds on the same runtime we use locally while also letting old commits build successfully during workflow_dispatch range backfills.
ci: pin release builds to node 25.9 The historical backfill run showed that many older commits predate .nvmrc, so actions/setup-node failed before the build even started. Pin the release workflow to Node 25.9.0 directly instead of reading the version from the checked-out commit. That keeps current builds on the same runtime we use locally while also letting old commits build successfully during workflow_dispatch range backfills.
ci: make ROM releases more descriptive Refresh the release workflow metadata so GitHub Releases feel less like raw artifacts and more like little build cards. Release titles now include the short commit SHA and commit subject, while the notes render a small changelog-style layout with the commit message, downloadable asset names, and build metadata. This keeps future per-commit ROM releases readable in the GitHub UI and works for both current kananeko artifacts and older historical builds.
ci: pin release builds to node 25.9 The historical backfill run showed that many older commits predate .nvmrc, so actions/setup-node failed before the build even started. Pin the release workflow to Node 25.9.0 directly instead of reading the version from the checked-out commit. That keeps current builds on the same runtime we use locally while also letting old commits build successfully during workflow_dispatch range backfills.
ci: pin release builds to node 25.9 The historical backfill run showed that many older commits predate .nvmrc, so actions/setup-node failed before the build even started. Pin the release workflow to Node 25.9.0 directly instead of reading the version from the checked-out commit. That keeps current builds on the same runtime we use locally while also letting old commits build successfully during workflow_dispatch range backfills.
ci: release every commit in a push Change the ROM release workflow from a single-ref build into a two-stage flow: a collector job resolves the exact commit SHAs to build, and the release job runs as a matrix over every commit in that set. On normal pushes to main this means every commit in the pushed range gets its own ROM prerelease, not just the tip commit. For manual backfills, workflow_dispatch now accepts either a single ref or a git revision range, so historical releases can be queued from the GitHub UI without keeping a separate helper script in the repository. Delete scripts/backfill-rom-releases.sh since the workflow itself now owns that backfill behavior.
ci: release every commit in a push Change the ROM release workflow from a single-ref build into a two-stage flow: a collector job resolves the exact commit SHAs to build, and the release job runs as a matrix over every commit in that set. On normal pushes to main this means every commit in the pushed range gets its own ROM prerelease, not just the tip commit. For manual backfills, workflow_dispatch now accepts either a single ref or a git revision range, so historical releases can be queued from the GitHub UI without keeping a separate helper script in the repository. Delete scripts/backfill-rom-releases.sh since the workflow itself now owns that backfill behavior.
PreviousNext