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
pull_request_target: # This workflow has permissions on the repo, do NOT run code from PRs in this workflow. See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
9
+
types:
10
+
- labeled
11
+
- unlabeled
12
+
branches:
13
+
- master
14
+
15
+
concurrency:
16
+
group: plan-release # only the latest one of these should ever be running
This PR is a preview of the release that [release-plan](https://github.com/embroider-build/release-plan) has prepared. To release you should just merge this PR 👍
Copy file name to clipboardExpand all lines: RELEASE.md
+20-13Lines changed: 20 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,15 @@ During the release week each of the versions are effectively "promoted" i.e. the
16
16
17
17
The release process during release week should look like this:
18
18
19
+
- Make sure that `@ember/app-blueprint` is released before starting any of these steps
19
20
- Merge any outstanding `Prepare Alpha Release` branches
20
21
- Do an intial stable release from the `release` branch
21
22
- Merge `release` into `beta`
22
23
- Do a `beta` release
23
24
- Merge `beta` into `master`
24
25
- Do an `alpha` release
25
26
26
-
###Merge any outstanding `Prepare Alpha Release` branches
27
+
###Merge any outstanding `Prepare Alpha Release` branches
27
28
28
29
This makes sure that you are starting from a "clean slate" before doing any other releases. This will make each of the following steps easier to follow.
29
30
@@ -38,19 +39,20 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
38
39
- Merge `origin/beta` into the release branch
39
40
-`git merge origin/beta --no-ff`
40
41
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
41
-
-**make sure to not update the .github/workflows/plan-release.yml file** this should still plan a stable release
42
-
-**make sure to not update the .github/workflows/publish.yml file** this should still publish a stable release
42
+
-**make sure to not update the .github/workflows/plan-stable-release.yml file** this should still plan a stable release
43
+
-**make sure to not update the .github/workflows/publish-stable.yml file** this should still publish a stable release
43
44
-**make sure to not update the CHANGELOG.md file** so as not to include the beta or alpha changelogs in the next release
44
45
- make sure to not update the version in the package.json during this step, this will be release-plan's job
46
+
- 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
45
47
- 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.
46
-
- Update blueprint dependencies to latest
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.
node ./dev/update-blueprint-dependencies.js --ember-source=latest --ember-data=<whatever version was in the beta>
50
52
```
51
53
52
54
- commit this update `git commit -am "update blueprint dependencies to latest"`
53
-
- push and open a PR targeting `release` with a PR title like `Update all dependencies for 6.4 release`
55
+
- push and open a PR targeting `release` with a PR title like `Promote Beta and update all dependencies for 6.4 release`
54
56
- mark this PR as an `enhancement` if it is a minor release
55
57
- check that everything is ok (i.e. that CI has run correctly and that you have the changes you expect)
56
58
- merge branch
@@ -64,26 +66,30 @@ You can use [this saved search](https://github.com/ember-cli/ember-cli/pulls?q=i
64
66
- create a new branch to merge `release` into `beta` e.g. `git checkout --no-track -b merge-release origin/beta`
65
67
- merge release into this new branch e.g. `git merge origin/release --no-ff`
66
68
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
67
-
-**make sure to not update any .github/workflows/plan-release.yml file** this should still plan a beta release
68
-
-**make sure to not update any .github/workflows/publish.yml file** this should still publish a beta release
69
+
-**make sure to not update any .github/workflows/plan-beta-release.yml file** this should still plan a beta release
70
+
-**make sure to not update any .github/workflows/publish-beta.yml file** this should still publish a beta release
69
71
- make sure to not update the version in the package.json during this step, that step comes later
70
72
- 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.
71
73
- merge master into this new branch too e.g. `git merge origin/master --no-ff`
72
74
-**make sure to not update the .release-plan file** this should only ever be changed by the release-plan github scripts
73
75
-**make sure to not update the CHANGELOG.md file** in this step. It should match the changelog on `origin/release` at this stage.
76
+
- make sure not to update the `release-plan` config in `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`
77
+
- commit the merge `git commit -am "merge master into beta"`
78
+
- update the versions in package.jsons
74
79
- 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",`
75
80
- update the alpha version in `packages/addon-blueprint/package.json` to be a beta
76
81
- update the alpha version in `packages/app-blueprint/package.json` to be a beta
77
-
- make sure not to update the `release-plan` config in `package.json`, `packages/addon-blueprint/package.json`, or `packages/app-blueprint/package.json`
78
82
- 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
83
+
- commit the version changes `git commit -am "update versions"`
0 commit comments