Skip to content

chore(main): release 1.0.2 - #8

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--opencode-caveman
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--opencode-caveman

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.0.2 (2026-09-17)

Bug Fixes

  • ci: declare release-please job outputs so publish runs (#7) (942ac0b)

This PR was generated with Release Please. See documentation.

@miguelmartens

Copy link
Copy Markdown
Owner

Closing rather than publishing. This PR exists because #7 landed as fix(ci): ... — release-please treats fix: commits as releasable units. But #7 only changed .github/workflows/release.yml, which is not part of the published npm tarball, so 1.0.2 would be a version bump with zero user-facing content. The fix will ride along in the next release that carries real changes (which will also be 1.0.2). Tooling-only changes will use chore(ci): from here on so they don't open release PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant