You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Releases in this repo are mostly automated using [release-plan](https://github.com/embroider-build/release-plan/). Once you label all your PRs correctly (see below) you will have an automatically generated PR that updates your CHANGELOG.md file and a `.release-plan.json` that is used to prepare the release once the PR is merged.
7
4
8
5
## Preparation
9
6
10
-
Since the majority of the actual release process is automated, the primary
11
-
remaining task prior to releasing is confirming that all pull requests that
12
-
have been merged since the last release have been labeled with the appropriate
13
-
`lerna-changelog` labels and the titles have been updated to ensure they
14
-
represent something that would make sense to our users. Some great information
15
-
on why this is important can be found at
16
-
[keepachangelog.com](https://keepachangelog.com/en/1.0.0/), but the overall
7
+
Since the majority of the actual release process is automated, the remaining tasks before releasing are:
8
+
9
+
- correctly labeling **all** pull requests that have been merged since the last release
10
+
- updating pull request titles so they make sense to our users
11
+
12
+
Some great information on why this is important can be found at [keepachangelog.com](https://keepachangelog.com/en/1.1.0/), but the overall
17
13
guiding principle here is that changelogs are for humans, not machines.
18
14
19
15
When reviewing merged PR's the labels to be used are:
20
16
21
-
* breaking - Used when the PR is considered a breaking change.
22
-
* enhancement - Used when the PR adds a new feature or enhancement.
23
-
* bug - Used when the PR fixes a bug included in a previous release.
24
-
* documentation - Used when the PR adds or updates documentation.
25
-
* internal - Used for internal changes that still require a mention in the
26
-
changelog/release notes.
17
+
- breaking - Used when the PR is considered a breaking change.
18
+
- enhancement - Used when the PR adds a new feature or enhancement.
19
+
- bug - Used when the PR fixes a bug included in a previous release.
20
+
- documentation - Used when the PR adds or updates documentation.
21
+
- internal - Internal changes or things that don't fit in any other category.
27
22
23
+
**Note:**`release-plan` requires that **all** PRs are labeled. If a PR doesn't fit in a category it's fine to label it as `internal`
28
24
29
25
## Release
30
26
31
-
Once the prep work is completed, the actual release is straight forward:
32
-
33
-
* First, ensure that you have installed your projects dependencies:
34
-
35
-
```
36
-
pnpm install
37
-
```
38
-
39
-
* Second, ensure that you have obtained a
40
-
[GitHub personal access token][generate-token] with the `repo` scope (no
41
-
other permissions are needed). Make sure the token is available as the
[release-it](https://github.com/release-it/release-it/) manages the actual
59
-
release process. It will prompt you to to choose the version number after which
60
-
you will have the chance to hand tweak the changelog to be used (for the
61
-
`CHANGELOG.md` and GitHub release), then `release-it` continues on to tagging,
62
-
pushing the tag and commits, etc.
27
+
Once the prep work is completed, the actual release is straight forward: you just need to merge the open [Plan Release](https://github.com/emberjs/ember-inspector/pulls?q=is%3Apr+is%3Aopen+%22Prepare+Release%22+in%3Atitle) PR
0 commit comments