Unexpected Changesets

The following changeset(s) reference packages that have not been changed in this PR:

• .changeset/cold-coins-speak.md: @backstage/app-defaults, @backstage/catalog-client, @backstage/catalog-model, @backstage/config, @backstage/core-app-api, @backstage/core-components, @backstage/core-plugin-api, @backstage/dev-utils, @backstage/errors, @backstage/frontend-app-api, @backstage/frontend-plugin-api, @backstage/integration, @backstage/integration-react, @backstage/release-manifests, @backstage/test-utils, @backstage/theme, @backstage/types, @backstage/version-bridge

Note that only changes that affect the published package require changesets, for example changes to tests and storybook stories do not require changesets.

Changed Packages

Uffizzi Ephemeral Environment deployment-35545

☁️ https://app.uffizzi.com/github.com/backstage/backstage/pull/19855

📄 View Application Logs etc.

What is Uffizzi? Learn more!

Your changeset lists a lot of unchanged packages, as you'll see - and the end to end tests don't like this.

The change impacts how those packages are generated. What is the best method to ensure those packages are updated with this change?

Hm in that case, should the changeset contain every single ESM enabled package, such as all plugins/ folder frontend, react, and common packages?

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!