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

Support graduating prereleases #26

Open
timcreatedit opened this issue Jan 9, 2025 · 1 comment
Open

Support graduating prereleases #26

timcreatedit opened this issue Jan 9, 2025 · 1 comment

Comments

@timcreatedit
Copy link

timcreatedit commented Jan 9, 2025

I'm struggling to understand what the intended workflow for prereleases is. I would've thought that if I version as prerelease using an action similar to the recommended workflow_dispatch-based one, the next time I run version without setting the prerelease flag, it would automatically graduate all releases.

Instead, if I versioned a prerelease on main once, I can't get out of this prerelease using the melos action.

This can of course be solved by running melos version -g locally and merging that into main, but I would've preferred an automated workflow

@spydon
Copy link
Member

spydon commented Jan 9, 2025

True, we have to add a proxy for the -g (graduate) flag.
If you feeling like putting up a PR for it I could publish a new version, it would look almost identical to the pre-release option:
https://github.com/bluefireteam/melos-action/blob/main/action.yml#L82-L85

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

No branches or pull requests

2 participants