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
Copy file name to clipboardExpand all lines: RELEASE.md
+24-6Lines changed: 24 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,12 +44,17 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
44
44
- make sure to not update the version in the package.json during this step, this will be release-plan's job
45
45
- make sure to not update the version in the `packages/app-blueprint/package.json`, or `packages/addon-blueprint/package.json` files during this step, this will be release-plan's job
46
46
- make sure to not add the `release-plan` config section to the package.json during this step. We are releasing a real release so we don't want to configure release-plan to do a pre-release.
47
+
- commit the merge `git commit -am "promote beta to release"`
47
48
- Update blueprint dependencies to latest. Note: ember-data needs to be updated only in the alpha version from now on, make sure to only update to the release version of what was in the beta.
48
49
49
50
```
50
51
node ./dev/update-blueprint-dependencies.js --ember-source=latest --ember-data=<whatever version was in the beta>
51
52
```
52
53
54
+
- run `pnpm lint:fix`
55
+
- update the @ember/app-blueprint dependency `pnpm i -w @ember/app-blueprint@latest`
56
+
- manually add a `~` back into the `@ember/app-blueprint` dependency in the root package.json
57
+
- run `pnpm install` to make sure the lock file is up to date
53
58
- commit this update `git commit -am "update blueprint dependencies to latest"`
54
59
- push and open a PR targeting `release` with a PR title like `Promote Beta and update all dependencies for 6.4 release`
55
60
- mark this PR as an `enhancement` if it is a minor release
@@ -59,6 +64,11 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
59
64
- Merge the `Prepare Release` branch when you are ready to release
60
65
- Check the `Release Stable` GitHub action to make sure the release succeeded
61
66
67
+
### Finish the `@ember/app-blueprint` release
68
+
69
+
- Update the `@ember/app-blueprint``release` branch to use this new version of ember-cli
70
+
- continue the rest of the [@ember/app-blueprint release process](https://github.com/ember-cli/ember-app-blueprint/blob/main/RELEASE.md#release-ember-cli-and-update-that-dependency) until beta and alpha are released
71
+
62
72
### Beta release from the `beta` branch
63
73
64
74
- fetch latest from origin `git fetch`
@@ -67,17 +77,20 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
67
77
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
68
78
-**make sure to not update any .github/workflows/plan-beta-release.yml file** this should still plan a beta release
69
79
-**make sure to not update any .github/workflows/publish-beta.yml file** this should still publish a beta release
70
-
- make sure to not update the version in the package.json during this step, that step comes later
80
+
- make sure to not update the version in the `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json` during this step, that step comes later
71
81
- make sure to not remove the `release-plan` config section to the `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`, during this step.
82
+
- commit the merge `git commit -am "merge release into beta"`
72
83
- merge master into this new branch too e.g. `git merge origin/master --no-ff`
73
84
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
74
85
-**make sure to not update the CHANGELOG.md file** in this step. It should match the changelog on `origin/release` at this stage.
75
86
- make sure not to update the `release-plan` config in `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`
87
+
- make sure not to update the `@ember-tooling/blueprint-blueprint` versions (i.e. not workspace dependencies) in `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`
88
+
- make sure not to add any files from `packages/blueprint-blueprint` or `packages/blueprint-model` in this merge (those files only exist on main)
76
89
- commit the merge `git commit -am "merge master into beta"`
77
90
- update the versions in package.jsons
78
91
- update the alpha version in package.json to be a beta i.e. if the incoming merge is `"version": "6.6.0-alpha.3",` update it to `"version": "6.6.0-beta.0",`
79
-
- update the alpha version in `packages/addon-blueprint/package.json` to be a beta
80
-
- update the alpha version in `packages/app-blueprint/package.json` to be a beta
92
+
- update the alpha version in `packages/addon-blueprint/package.json` to be the same beta version
93
+
- update the alpha version in `packages/app-blueprint/package.json` to be the same beta version
81
94
- update the `ember-cli` reference in `packages/app-blueprint/files/package.json` to be the same as the version you just put in the top level package.json
82
95
- commit the version changes `git commit -am "update versions"`
83
96
- Update blueprint dependencies to beta
@@ -86,8 +99,10 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
86
99
node ./dev/update-blueprint-dependencies.js --ember-source=beta --ember-data=<whatever version was in the alpha>
87
100
```
88
101
102
+
- run `pnpm lint:fix`
89
103
- update the @ember/app-blueprint dependency `pnpm i -w @ember/app-blueprint@beta`
90
104
- manually add a `~` back into the `@ember/app-blueprint` dependency in the root package.json
105
+
- run `pnpm install` to make sure the lock file is up to date
91
106
- commit this update `git commit -am "update blueprint dependencies to beta"`
92
107
- push and open a PR targeting `beta` with a PR title like `Prepare 6.5-beta`
93
108
- mark this PR as an `enchancement` if the next beta is a minor release
@@ -104,9 +119,9 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
104
119
- create a new branch to merge `beta` into `master` e.g. `git checkout --no-track -b merge-beta origin/master`
105
120
- merge beta into this new branch e.g. `git merge origin/beta --no-ff`
106
121
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
107
-
- make sure to not update the version in the package.json during this step, that step comes later
122
+
- make sure to not update the version in the `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json` during this step, that step comes later
108
123
- make sure to not update the `release-plan` config section to the `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`, during this step.
109
-
- make sure not to update the `@ember-tooling/blueprint-blueprint` or `@ember-tooling/blueprint-model` away from being `workspace: *` dependencies. On master they always use the latest and don't use semver.
124
+
- make sure not to update the `@ember-tooling/blueprint-blueprint` or `@ember-tooling/blueprint-model` away from being `workspace: *` dependencies in `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`. On master they always use the latest and don't use semver.
110
125
-**make sure to not update any .github/workflows/plan-release.yml file** this should still plan a beta release
111
126
-**make sure to not update any .github/workflows/publish.yml file** this should still publish a beta release
112
127
-**make sure to not update the CHANGELOG.md file** in this step.
@@ -116,16 +131,19 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
116
131
- e.g. if the current alpha is `"version": "6.6.0-alpha.3",` update it to be `"version": "6.7.0-alpha.0",`
117
132
- manually update the alpha version in `packages/addon-blueprint/package.json` to be the same alpha
118
133
- manually update the alpha version in `packages/app-blueprint/package.json` to be the same alpha
119
-
- commit this change to the version in package.json: `git commit -am "update to the next alpha version"`
134
+
- update the `ember-cli` reference in `packages/app-blueprint/files/package.json` to be the same alpha
135
+
- commit this change `git commit -am "update to the next alpha version"`
120
136
- Update blueprint dependencies to alpha
121
137
122
138
```
123
139
node ./dev/update-blueprint-dependencies.js --ember-source=alpha --ember-data=<whatever version is in the package.json>
124
140
```
125
141
126
142
- note: ember-data (aka warp-drive) should only ever be updated on master as a separate PR. It is no longer part of the release process
143
+
- run `pnpm lint:fix`
127
144
- update the @ember/app-blueprint dependency `pnpm i -w @ember/app-blueprint@alpha`
128
145
- make sure the app-blueprint still has a `~` after the above step
146
+
- run `pnpm install` to make sure the lock file is up to date
129
147
- commit this update `git commit -am "update blueprint dependencies to alpha"`
130
148
- push and open a PR targeting `master` with a PR title like `Prepare 6.6-alpha`
131
149
- mark this PR as an `enchancement` if the next alpha is a minor release
0 commit comments