# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

Prepare 7.1 Alpha

Prepare Alpha Release

update @ember/optional-features

…-workflow

update ember-cli-deprecation-workflow to v4

update ember-welcome-page to v8 in app blueprint

Prepare Alpha Release

update configstore to v8

update RELEASE with update-blueprint-deps commands

update babel-remove-types to v2

When a tag push fires (e.g. v7.1.0-alpha.2-ember-cli), github.ref_name
already contains the full tag name including the -ember-cli suffix.
The old verify-inputs step was blindly appending -ember-cli again,
producing the doubled tag v7.1.0-alpha.2-ember-cli-ember-cli.
The regex in the scripts only strips one trailing -ember-cli, so the
npm version resolved to "7.1.0-alpha.2-ember-cli", which does not exist
on the registry.

Fix:
- Use github.ref_type == 'tag' to detect tag-push runs and use
  github.ref_name directly (without appending the suffix again).
- Narrow push.tags filter from v* to v*-ember-cli so only the
  ember-cli package tags trigger this workflow.

Agent-Logs-Url: https://github.com/ember-cli/ember-cli/sessions/4c5503b9-afaa-4ccd-8a15-f0501be7ea4b

Co-authored-by: kategengler <444218+kategengler@users.noreply.github.com>

…ag-workflow

Added instructions to check the Sync Output Repos GitHub action to ensure output repos are generated from the tag during release processes.

Add Sync Output Repos check to release instructions

use semver-deprecate instead of internal code

Update diff to latest v8.x

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

Prepare Alpha Release

Promote Beta and update all dependencies for 7.0 release

Prepare Stable Release

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

# Conflicts:
#	CHANGELOG.md
#	package.json
#	packages/app-blueprint/files/package.json
#	pnpm-lock.yaml
#	tests/fixtures/addon/defaults/package.json
#	tests/fixtures/addon/pnpm/package.json
#	tests/fixtures/addon/typescript/package.json
#	tests/fixtures/addon/yarn/package.json
#	tests/fixtures/app/defaults/package.json
#	tests/fixtures/app/embroider-no-ember-data/package.json
#	tests/fixtures/app/embroider-no-welcome/package.json
#	tests/fixtures/app/embroider-pnpm/package.json
#	tests/fixtures/app/embroider-yarn/package.json
#	tests/fixtures/app/embroider/package.json
#	tests/fixtures/app/nested-project/actual-project/package.json
#	tests/fixtures/app/no-ember-data/package.json
#	tests/fixtures/app/npm/package.json
#	tests/fixtures/app/pnpm/package.json
#	tests/fixtures/app/typescript-embroider-no-ember-data/package.json
#	tests/fixtures/app/typescript-embroider/package.json
#	tests/fixtures/app/typescript-no-ember-data/package.json
#	tests/fixtures/app/typescript/package.json
#	tests/fixtures/app/with-blueprint-override-lint-fail/package.json
#	tests/fixtures/app/yarn/package.json