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
- commit this update `git commit -am "update blueprint dependencies to alpha"`
@@ -147,6 +150,22 @@ You can use [this saved search](https://github.com/ember-cli/ember-app-blueprint
147
150
- Merge the `Prepare Alpha Release` when you are ready to release the next alpha version
148
151
- Check the `Release Alpha` GitHub action to make sure the release succeeded
149
152
153
+
### Update all packages
154
+
155
+
In the `update-blueprint-deps` steps described above we updated all packages that had in-range updates available. We also need to apply any out-of-range updates as part of the release process.
156
+
157
+
Once the Alpha release has been completed we should run the following command to see if there are any releases that have out-of-range updates available:
This is not intended to be committed and opened as a single PR, it is for illustrative purposes only. If your git diff shows that there are any packages that need to have the range updated (i.e. we have a `^` dependency defined but there is a new major release available) then you should run the same command to update that package with a filter on the package name e.g.
0 commit comments