Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semantic release preview on PRs #418

Open
martimalek opened this issue Feb 5, 2024 · 1 comment
Open

Semantic release preview on PRs #418

martimalek opened this issue Feb 5, 2024 · 1 comment
Labels
CI/CD Efforts that will impact our integration/deployment pipeline enhancement New feature or request

Comments

@martimalek
Copy link
Contributor

Describe the feature you'd like

We use semantic-release to automatically release new library versions when a PR is merged to main.

From time to time we've had some unexpected versions released due to having created commits with the wrong type. It would be interesting to have a way to preview the version number that semantic release will use before we merge to the branch.

I've started making some tries in PR #414 through a Github Action.

Describe alternatives you've considered

This is not a must so we don't need to do it, but it would avoid confusion on certain releases.

@martimalek martimalek added CI/CD Efforts that will impact our integration/deployment pipeline enhancement New feature or request labels Feb 5, 2024
@nlopin
Copy link
Contributor

nlopin commented Feb 5, 2024

We can also consider a semi-automatic approach when a release is triggered manually. We keep a changeset using https://github.com/changesets/changesets and publish it when we think it makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Efforts that will impact our integration/deployment pipeline enhancement New feature or request
Development

No branches or pull requests

2 participants