Skip to content

ci: configure next branch releases#2388

Merged
rafaelcr merged 1 commit intonextfrom
ci/next
Dec 3, 2025
Merged

ci: configure next branch releases#2388
rafaelcr merged 1 commit intonextfrom
ci/next

Conversation

@rafaelcr
Copy link
Collaborator

@rafaelcr rafaelcr commented Dec 3, 2025

Configures the next branch to generate API prereleases (e.g. v9.0.0-next.1).

Also, changes the default @semantic-release/github behavior to not automatically publish releases but use drafts only instead, so we can:

  1. Choose not to publish one when it's not necessary (like next or beta) to avoid confusing exchanges and other partners subscribed to the releases feed
  2. Pre-edit the release contents with our rich markdown format before issuing the actual release

@semantic-release/github does not have a way to select which branches generate releases.

@github-actions
Copy link

github-actions bot commented Dec 3, 2025

Vercel deployment URL: https://stacks-blockchain-ceyefj8bz-hirosystems.vercel.app 🚀

@codecov
Copy link

codecov bot commented Dec 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Contributor

@CharlieC3 CharlieC3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: LGTM!

@rafaelcr rafaelcr merged commit 895b3e3 into next Dec 3, 2025
27 checks passed
@rafaelcr rafaelcr deleted the ci/next branch December 3, 2025 21:00
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.

2 participants