Skip to content

@W-2256867@ chore: bump @salesforce/templates to ^66.9.1#953

Merged
iowillhoit merged 1 commit into
salesforcecli:mainfrom
sf-manan-jhaveri:mj/fix-lockfile-registry-url
Jun 2, 2026
Merged

@W-2256867@ chore: bump @salesforce/templates to ^66.9.1#953
iowillhoit merged 1 commit into
salesforcecli:mainfrom
sf-manan-jhaveri:mj/fix-lockfile-registry-url

Conversation

@sf-manan-jhaveri
Copy link
Copy Markdown
Contributor

@W-2256867@

Bumps @salesforce/templates from ^66.9.0 to ^66.9.1.

Why

@salesforce/templates@66.9.1 picks up the new @salesforce/ui-bundle-template-*@9.x content, which adds:

  • force-app/main/default/applications/<name>.app-meta.xml<CustomApplication> metadata
  • force-app/main/default/permissionsets/<name>_Access.permissionset-meta.xml
  • <target>CustomApplication</target> in <name>.uibundle-meta.xml

Without this bump, sf template generate project --template reactinternalapp (or --template reactexternalapp) produces a project missing those files. End users have to add the customApplication metadata by hand.

Test

sf template generate project --template reactinternalapp --name myapp -d /tmp
ls /tmp/myapp/force-app/main/default/applications/   # expect: myapp.app-meta.xml

@iowillhoit iowillhoit merged commit 664efc3 into salesforcecli:main Jun 2, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants