Skip to content

ci: create GitHub release after publish - #2609

Merged
joshuaellis merged 1 commit into
nextfrom
ci/release-gh-release
Oct 1, 2026
Merged

joshuaellis merged 1 commit into
nextfrom
ci/release-gh-release

Conversation

@joshuaellis

Copy link
Copy Markdown
Member

Publishing from next now creates the v<version> tag and GitHub release, marked as a pre-release for beta versions. Until now both were made by hand after every publish.

The changesets action only creates per-package tags. It skips GitHub releases because CHANGELOG.md is gitignored in this repo.

@changeset-bot

changeset-bot Bot commented Oct 1, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 26ac8ed

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@joshuaellis
joshuaellis merged commit 72cdaf4 into next Oct 1, 2026
14 checks passed
@joshuaellis
joshuaellis deleted the ci/release-gh-release branch October 1, 2026 07:51
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