Skip to content

Revert "chore(release): v0.1.2-rc.10 (#477)" - #478

Merged
spiral-ladder merged 1 commit into
mainfrom
bing/revert-v0.1.2
Jul 9, 2026
Merged

Revert "chore(release): v0.1.2-rc.10 (#477)"#478
spiral-ladder merged 1 commit into
mainfrom
bing/revert-v0.1.2

Conversation

@spiral-ladder

Copy link
Copy Markdown
Member

This reverts commit 9a4fad5.

@spiral-ladder spiral-ladder self-assigned this Jul 9, 2026
@spiral-ladder
spiral-ladder requested a review from a team as a code owner July 9, 2026 17:35
@spiral-ladder
spiral-ladder merged commit d9b582c into main Jul 9, 2026
5 of 6 checks passed
wemeetagain added a commit that referenced this pull request Jul 30, 2026
## Motivation

Our release process is manual and opaque: versions are hand-bumped in
`package.json` via PR, tags and GitHub releases are created by hand, and
publishing is a manual `workflow_dispatch` runnable on any ref. This has
led to drift — right now `v0.1.2-rc.10` is on npm and GitHub releases,
but its tag points to a commit that isn't on `main`, and `main`'s
`package.json` still says `0.1.2-rc.9` (see #477 / #478).

Resolves #505

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: bing <spiralladder@fastmail.com>
Co-authored-by: matthewkeil <me@matthewkeil.com>
Co-authored-by: Matthew Keil <github@mail.matthewkeil.com>
@wemeetagain
wemeetagain deleted the bing/revert-v0.1.2 branch August 17, 2026 19:47
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