Skip to content

feat: one release process for every chunkzero project - #1

Merged
oglassdev merged 7 commits into
mainfrom
feat/release-actions
Oct 5, 2026
Merged

oglassdev merged 7 commits into
mainfrom
feat/release-actions

Conversation

@oglassdev

Copy link
Copy Markdown
Contributor

Chunk, RPP and Window each carry their own copy of a release script, and the copies have drifted: date-only nightly versions that collide within a day, deletion of everything past the newest 30 nightlies (which breaks exact pins and lockfiles), and no shared way to publish CLI archives for mise.

This adds three composite actions every project can use:

  • version: computes the build's version once from the project's upcoming release. Nightlies are <x.y.z>-nightly.<UTC commit time>.g<sha12>, so the same commit always gets the same version, and the output reports whether that version is already public.
  • publish: uploads to a draft, re-downloads and compares every asset, then publishes. Published releases are never modified or deleted; prereleases are never marked latest.
  • mise-registry: opens an auto-merging PR that adds the release to chunkzero/mise-registry.

Checks: python3 -m unittest test_release.py (6 tests, passing).

🤖 Generated with Claude Code

@oglassdev
oglassdev merged commit cc39f42 into main Oct 5, 2026
1 check passed
@oglassdev
oglassdev deleted the feat/release-actions branch October 5, 2026 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant