docs/releases/v1.53.0-next.2-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.53.0-next.2
wrapInOpenApiTestServer. This function redirected test traffic through the Optic capture proxy via the OPTIC_PROXY environment variable. Since the Optic dependency has been removed, this function no longer serves a purpose. Use wrapServer instead for OpenAPI spec validation in tests.bootstrapEnvProxyAgents export along with the global-agent and undici dependencies. Use Node.js built-in proxy support by setting NODE_USE_ENV_PROXY=1 alongside your HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables instead. See the corporate proxy guide for details.versions:bump command no longer bootstraps legacy proxy agents. Use Node.js built-in proxy support by setting NODE_USE_ENV_PROXY=1 alongside your HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables instead.NODE_USE_ENV_PROXY=1 alongside your HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables instead.84171b3: BREAKING: Replaced @useoptic/optic and @useoptic/openapi-utilities with oasdiff for OpenAPI breaking change detection.
To migrate, remove @useoptic/optic from your root package.json and install the oasdiff CLI on your system — see https://github.com/oasdiff/oasdiff#installation for instructions.
The package schema openapi diff command now uses oasdiff under the hood. The --since, --json, and --ignore flags continue to work, but the JSON and text output formats have changed to match oasdiff's native output.
The repo schema openapi diff command now automatically detects all packages with a changed src/schema/openapi.yaml and runs oasdiff against them directly. Packages no longer need a "diff" script in their package.json to be included in the check.
Removed the package schema openapi init and repo schema openapi test commands, which depended on the Optic capture workflow and have no equivalent with oasdiff. Runtime validation of your API against its OpenAPI spec is still available via wrapServer from @backstage/backend-openapi-utils/testUtils.
connection config option for the Redis cache store now accepts either a string URL or an object with additional connection options that are passed directly to the underlying client. The object form is only supported when backend.cache.store is redis; other stores require a plain string. This allows configuring options like pingInterval without needing dedicated config fields. For clustered Redis, the connection object properties are merged into cluster defaults. Fixes https://github.com/backstage/backstage/issues/31813, https://github.com/backstage/backstage/issues/31742./v1/revoke endpoint is now available whenever dynamic client registration or client ID metadata documents are enabled, and is advertised through revocation_endpoint in the OpenID provider configuration.prompt setting for Auth0 authorization requests. Set it to
auto to let Auth0 determine whether the user needs to be prompted. Existing
configurations continue to use consent by default.EntityTypePicker's initialFilter prop was being cleared when used alongside EntityKindPicker inside EntityListProvider. The type filter is now correctly preserved after the available types load for the selected kind.DatabaseTaskStore.list returning totalTasks as a string on PostgreSQL. knex returns a COUNT(*) aggregate as a string on PostgreSQL (the column is a bigint) while better-sqlite3 returns a number, so the count is now coerced with Number(...) and guarded with Number.isSafeInteger(...). This in turn fixes the list-scaffolder-tasks action, whose output schema declares totalTasks: z.number() and previously failed validation in production with Invalid output ... totalTasks: Expected number, received string.