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.

Sign up for GitHub

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

Jump to bottom

Investigate seeing the next version before the deploy #356

Open
yanick opened this issue Apr 18, 2024 · 1 comment · May be fixed by #373
Open

Investigate seeing the next version before the deploy #356

yanick opened this issue Apr 18, 2024 · 1 comment · May be fixed by #373

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

mcous added a commit that referenced this issue May 1, 2024
@mcous
ci(release): use semantic-release directly, add release preview script
a4cafa5 
Closes #356
@mcous mcous linked a pull request May 1, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@yanick @mcous