From 670765908e099cebc445920a4cd8a1c5961ef61d Mon Sep 17 00:00:00 2001 From: Ricardo Mendes Date: Thu, 11 Sep 2025 10:41:16 +0100 Subject: [PATCH] Update ember-releases.md --- ember-releases.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/ember-releases.md b/ember-releases.md index 4189f81..8885cae 100644 --- a/ember-releases.md +++ b/ember-releases.md @@ -48,12 +48,7 @@ defaults to the Ember Learning Team. ⚠️ WAIT! ⚠️ - Please ensure that Ember, Ember CLI and EmberData have each released before proceeding -We have a CLI tool called [`tool-new-release`](https://github.com/ember-learn/tool-new-release) that automates many of the below steps and is recommended. Each of those automated steps has a manual fallback process. - -- install `tool-new-release` - this automates most of the things (deprecated and soon will not be needed) - install 1Password and make sure you have access to the `Ember CLI` vault -- install `1password-cli` -- sign in to `1password-cli` - sign in to 1password `Ember CLI` vault ### Follow these release steps in this specific order: @@ -68,7 +63,6 @@ We have a CLI tool called [`tool-new-release`](https://github.com/ember-learn/to 1. [merge deprecations PR](#merge-deprecations-pr) 1. [Release pages](#release-pages) 1. [Upgrade Guide](#upgrade-guide) -1. [Glitch Ember starter](#glitch-ember-starter) 1. [Ember Wikipedia](#ember-wikipedia) 1. [Release bot](#release-bot) @@ -194,7 +188,6 @@ Note: The Wikipedia page may have already been updated automatically for the ver 💁 manual process - 1. Go to the core meta channel in Discord. 2. Mark current release as done with `/release-done blog`. 3. Schedule next release with the `/release-next ` command. E.g. `/release-next 3.26 03/22/2021`. Note, the date should likely be 6 weeks from the Monday that the current release week started with (regardless of how late we might be). https://wolframalpha.com/ can help with accurately calculating this date.