Skip to content

chore(release): 0.4.4-next.0#47

Closed
justin-carper wants to merge 2 commits into
mainfrom
chore/release-0.4.4-next.0
Closed

chore(release): 0.4.4-next.0#47
justin-carper wants to merge 2 commits into
mainfrom
chore/release-0.4.4-next.0

Conversation

@justin-carper

Copy link
Copy Markdown
Collaborator

Lands the version bump and CHANGELOG entry for the @next prerelease.

Why a PR?

Direct push to main is blocked by the repo's branch-protection rule (changes must go through a PR). The v0.4.4-next.0 tag was pushed and the Release workflow already published @stablekernel/[email protected] to the next dist-tag — but the version-bump commit (0.4.4-next.0) and the CHANGELOG entry only exist locally. This PR lands them on main so the published version and main's package.json agree.

Contents

Verification

  • Release workflow run #28112319705 — all steps green (typecheck, test, build, integration smoke test, npm publish to next, GitHub prerelease created)
  • npm view @stablekernel/opencode-cursor dist-tagsnext: 0.4.4-next.0

Merge target: main. This only adds the version bump + changelog; no code changes.

Document the redundant thinking-variant suppression in [Unreleased]
alongside the version bump to 0.4.4-next.0.
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