[rush] `init-deploy --project=<target-project>` fails with missing `scenario-template.json` after Rush dependency upgrade

[koen-dev]

Summary

After upgrading Rush-related dependencies in our monorepo (latest commit is an "Upgrade Rush-related dependencies" change), rush init-deploy --project=<target-project> started failing consistently.

We are trying to generate deploy config for a single project, but Rush fails because it cannot find rush-init-deploy/scenario-template.json under @microsoft/rush-lib.

Repro steps

1. In a Rush monorepo, update Rush-related dependencies (in our case this happened in a recent dependency-upgrade commit).

2. Ensure the repo is installed (rush install).

3. Run:

   rush init-deploy --project=<target-project>

4. Observe the error below.

Expected result: Rush initializes deploy artifacts for the selected project.

Actual result: Rush exits with ENOENT for scenario-template.json:

ERROR: File does not exist:
<workspace-root>/common/temp/install-run/@microsoft+rush@5.170.1/node_modules/@microsoft/rush-lib/assets/rush-init-deploy/scenario-template.json
File does not exist:
<workspace-root>/common/temp/install-run/@microsoft+rush@5.170.1/node_modules/@microsoft/rush-lib/assets/rush-init-deploy/scenario-template.json
ENOENT: no such file or directory, open
'<workspace-root>/common/temp/install-run/@microsoft+rush@5.170.1/node_modules/@microsoft/rush-lib/assets/rush-init-deploy/scenario-template.json'

Details

It looks like the file expected by rush init-deploy is missing from the installed @microsoft/rush-lib package path for Rush 5.170.1 in our environment.

Possible causes:

• packaging regression for @microsoft/rush-lib assets,
• changed asset path not reflected in init-deploy,
• corrupted local Rush install cache.

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question	Answer
@microsoft/rush globally installed version?	5.170.1
rushVersion from rush.json?	5.170.1
pnpmVersion, npmVersion, or yarnVersion from rush.json?	pnpm@10.29.2
(if pnpm) useWorkspaces from pnpm-config.json?	true
Operating system?	macOS
Would you consider contributing a PR?	Yes
Node.js version (node -v)?	v22.22.0

[koen-dev]

Here you can see the file tree structure of 5.169.3:

And this one is from 5.170.1:

[bosconian-dynamics]

I'll second this.

I've had both rush init (using a global rush install) as well as npx --yes -p @microsoft/rush@latest rush init fail with a similar error about missing templates, though in the case of my plain 'ol init the template file in question is @microsoft/rush-lib/assets/rush-init/[dot]github/workflows/ci.yml.

The point of failure is the same: @microsoft/rush-lib/assets does not exist.

Downgrading to 5.169.3 has mitigated the issue with init for me. I've subsequently bumped the project back up to 5.170.1 and have not experienced further issues in general usage - though I reckon any other operations which depend on those templates would continue to fail.

[iclanton]

Sorry about this. This should be fixed in v5.171.0