Skip to content

Investigate seeing the next version before the deploy #356

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

Closed
yanick opened this issue Apr 18, 2024 · 2 comments
Closed

Investigate seeing the next version before the deploy #356

yanick opened this issue Apr 18, 2024 · 2 comments

Comments

@yanick
Copy link
Collaborator

yanick commented Apr 18, 2024

Right now, merges that aren't triggering a release don't show what would be the next version (I... think). See if we can tweak the semantic release action to always give us a head's up on what would be the next release, because I keep putting my deployment foot in my mouth, so to speak.

@mcous
Copy link
Collaborator

mcous commented Apr 18, 2024

I was looking into the dry-run option for this! But I failed entirely to get it working locally so I gave up. But I agree this would be an excellent change if we could get it to work

Copy link

🎉 This issue has been resolved in version 5.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants