Skip to content

Start using release-plan for releasing ember-cli#10699

Merged
mansona merged 6 commits intomasterfrom
release-plan
Jun 9, 2025
Merged

Start using release-plan for releasing ember-cli#10699
mansona merged 6 commits intomasterfrom
release-plan

Conversation

@mansona
Copy link
Member

@mansona mansona commented May 21, 2025

This PR starts the proposed change to start using release-plan for releasing ember-cli. This will allow us to unblock #10671 since that PR is changing ember-cli to be a monorepo with multiple packages released

There are a few todo items in this PR but I'm opening it slightly early to get some feedback 👍

@mansona mansona marked this pull request as ready for review May 28, 2025 12:55
git fetch origin
git checkout -B release --track origin/release
```
### Initial Stable Release from the `release` branch
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this missing the step of merging the other branches?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I've read through it all a bit more and I wasn't exactly clear which branches you were talking about 🤔 I have made things a bit more clear in the latest commit so hopefully that clears it up. Can you let me know 👍

git fetch origin
git checkout -B beta --track origin/beta
```
If you want to change the content of the Changelog then you should update the PR titles you want to update and re-run the `Prepare Release` CI job for that branch
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is worth noting that the file can be edited on the Prepare Release PR right before merging. We may want to do that to add any particular notes for things that don't have PRs.

* Release: `npx release-it`
* Update GitHub Release with changelog contents
* Merge `beta` into `master` branch
Now that we're using release-plan for all releases, patch releases have become super easy! Every time you merge a PR to any branch that is being released with `release-plan` a new `Prepare Release` PR will be created. When you merge this `Prepare Release` branch it will automatically release the new Patch version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do I release a patch to an older version? LTSes are more common but occasionally we do have bug fixes or security fixes to prior versions.

@kategengler kategengler requested a review from kellyselden May 28, 2025 18:21
@kategengler
Copy link
Member

@kellyselden Since you do the releases we'd appreciate your review here

@kategengler
Copy link
Member

I don't think the comments should block -- just keep them in mind when filling out the documentation.

@mansona mansona merged commit 92acf21 into master Jun 9, 2025
206 of 207 checks passed
@mansona mansona deleted the release-plan branch June 9, 2025 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants