chore: release main - #1
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
August 24, 2026 08:20
b612ca5 to
631673c
Compare
HaydenBruin
added a commit
that referenced
this pull request
Aug 24, 2026
Replaces release-please with semantic-release, because the two tools have different release models and the one that was installed cannot do what is wanted here. release-please is PR-based by design: it opens a release PR and nothing is tagged until a human merges it. There is no mode that skips that. semantic-release does the whole thing in the push that lands the work — reads the commits, picks the version, tags, writes the release notes, publishes. It also fixes why merging release PR #1 produced no release at all. The job reported success, but its log carried: Error: unexpected token ' ' at 1:6, valid tokens [(, !, :] That is release-please's conventional-commit parser throwing on "Merge pull request #1 from engineio/release-please--branches--main" — `Merge` is five characters and then a space where it wanted `(`, `!` or `:`. It expects squash merges; given a merge commit it crashed parsing its own merge and never created the tag. semantic-release's analyser skips non-conforming subjects, and a dry run against this exact history confirms it: 16 commits analysed, next version 0.2.0. Tagged v0.1.0 at the initial commit as a baseline. Without a prior tag semantic-release treats the repo as unreleased and its first version is 1.0.0 — the same 0.x trap release-please had, reached a different way. Tagging the first commit makes everything after it compute to 0.2.0. Deliberately omits @semantic-release/changelog and @semantic-release/git, so nothing is written back to main. main requires pull requests, and a CI job pushing straight to it needs a bypass no automation should hold. Two consequences, both documented in the README: package.json's version is the placeholder 0.0.0-development (tags are the source of truth, and the real version is written in the runner just before publish), and there is no CHANGELOG.md because the release notes are the changelog. Two things the dry run caught that would have failed in CI: * conventional-changelog-conventionalcommits@10 needs conventional-changelog-writer@9, but semantic-release 25 bundles writer@8. Pinned the preset to @9. * Hex colours in commit bodies were being parsed as issue references, so the notes claimed "closes #FF006A" and linked to issues that do not exist. issuePrefixes now points at a token we never use. Also wires the gallery's version label to the release instead of a hardcoded string, since package.json can no longer supply it: the Pages build passes `git describe` in as DS_VERSION (hence the unshallow checkout) and a local `bun run dev` reads "dev". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.2.0
0.2.0 (2026-08-24)
⚠ BREAKING CHANGES
Features
Bug Fixes
Styling
This PR was generated with Release Please. See documentation.