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

Add "unstable" functionality #40

Open
mansona opened this issue Dec 13, 2023 · 2 comments
Open

Add "unstable" functionality #40

mansona opened this issue Dec 13, 2023 · 2 comments
Labels

Comments

@mansona
Copy link
Member

mansona commented Dec 13, 2023

release-plan was originally extracted from embroider to manage the release of a complicated monorepo tree of dependencies.

Embroider also has another feature, "unstable releases" that was not managed by release-plan because it pre-dates the creation of this package. The unstable releases always just do a next patch version and add -unstable.<sha> to the end but it would be nice to add this functionality to release-plan so it would actually be a major if the next release would be a major 👍

Here is the code for the unstable release: https://github.com/embroider-build/embroider/tree/main/test-packages/unstable-release

@RobbieTheWagner
Copy link

This sounds similar to what I need, I just need a way to specific prerelease for the GitHub release and an npm release channel, which could be alpha etc, as well as not just assuming a major version, but instead allowing overriding version numbers.

@patricklx
Copy link

patricklx commented Jan 24, 2025

i was looking for this just now.
I ended up with this, using the release-preview branch created by release-plan:

current_version=$(cat package.json | jq '.version')
next_version=$(curl https://api.github.com/repos/org/repo-name/contents/package.json?ref=release-preview | jq '.content' | base64 -D | jq '.version')
if [[ "$version" != "$next_version" ]]; then
  version="$next_version.$(date +s)-$(git rev-parse --short HEAD)"
  npm version $version
  npm publish
fi

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

No branches or pull requests

3 participants