RATATOSK
← All releases

Backstagev1.56.6

Security 5Breaking changes 2

Get Backstage alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Upgrade guide1
Upgrade Helper for upgrading to 1.56.6
Upgrade Helper: [https://backstage.github.io/upgrade-helper/?to=1.56.6](https://backstage.github.io/upgrade-helper/?to=1.56.6)
github.com/backstage/backstage/releases/tag/v1.56.6

Security5

Kubernetes proxy stops forwarding caller headers

AffectsKubernetes proxy requests to target clusters(Inferred)

Previously, these requests forwarded the caller's Authorization and Cookie headers. Upstream credentials now come only from the configured auth strategy or the Backstage-Kubernetes-Authorization header.

Show release-note lines
- fd7fe0c: Kubernetes proxy: stop forwarding the caller's `Authorization` and `Cookie` headers to the target cluster. Upstream requests now carry only credentials from the configured auth strategy or the `Backstage-Kubernetes-Authorization` header.
github.com/backstage/backstage/releases/tag/v1.56.6

Azure DevOps placeholder reads restricted to the entity’s own repository

Affectscatalog entity placeholders with a configured Azure DevOps integration

The restriction applies to legacy {org}.visualstudio.com and Azure DevOps Server hosts as well. Targets that cannot be attributed to a repository are rejected.

Show release-note lines
- e26964d: Improved repository validation for catalog entity placeholders on Azure DevOps. Placeholder-driven reads on a configured Azure DevOps integration are now restricted to the entity's own repository on every Azure DevOps host shape, including legacy `{org}.visualstudio.com` hosts and Azure DevOps Server hosts, and targets that cannot be attributed to a repository are rejected as well.
github.com/backstage/backstage/releases/tag/v1.56.6

Fetch-action credential host check fixed

Affectssetups with scaffolder.requireScmUserCredentials enabled
Additional actionscaffolder.requireScmUserCredentials enabled

Previously, fetch actions checked the template location's host instead of the host resolved from the fetch URL when those hosts differed. The check now uses the resolved host, including when the fetch URL is not parseable as an absolute URL on its own.

Show release-note lines
- e33b6d9: Check the host that relative fetch URLs resolve to when user credentials are required.
  When `scaffolder.requireScmUserCredentials` is enabled, the fetch actions now apply the user-credential requirement to the host that the fetch URL resolves to, rather than the host of the template location. This makes the requirement effective also for fetch URLs that are not parseable as absolute URLs on their own.
github.com/backstage/backstage/releases/tag/v1.56.6

Scaffolder actions reject paths outside the target repository

Affectssetups using the gitlab:repo:push, publish:gitlab:merge-request or publish:github:pull-request scaffolder actions

Absolute paths and paths containing .. segments are rejected in targetPath inputs and, for publish:github:pull-request, filesToDelete entries. Changes are applied only inside the intended repository subdirectory.

Show release-note lines
- b2d18d7: Validates the `targetPath` input of the `gitlab:repo:push`, `publish:gitlab:merge-request` and `publish:github:pull-request` scaffolder actions, and the `filesToDelete` entries of `publish:github:pull-request`. The values must be relative paths within the target repository; absolute paths and paths containing `..` segments are now rejected, so changes are only applied inside the intended subdirectory of the repository.
github.com/backstage/backstage/releases/tag/v1.56.6

GitLab scaffolder actions reject unsafe paths

AffectsGitLab scaffolder setups using gitlab:repo:push, publish:gitlab:merge-request or publish:github:pull-request, including filesToDelete in the latter

Absolute paths and paths containing .. segments are rejected in targetPath for these actions and in filesToDelete for publish:github:pull-request, restricting changes to relative paths within the target repository.

Show release-note lines
## @backstage/plugin-scaffolder-backend-module-gitlab@0.12.3
### Patch Changes
- b2d18d7: Validates the `targetPath` input of the `gitlab:repo:push`, `publish:gitlab:merge-request` and `publish:github:pull-request` scaffolder actions, and the `filesToDelete` entries of `publish:github:pull-request`. The values must be relative paths within the target repository; absolute paths and paths containing `..` segments are now rejected, so changes are only applied inside the intended subdirectory of the repository.
github.com/backstage/backstage/releases/tag/v1.56.6

Breaking changes2

validate-entity request location takes precedence over entity annotations

Affectssetups submitting entities with location annotations to the validate-entity endpoint

Previously, a submitted entity's location annotation could override the request location.

Show release-note lines
- e6e35ab: Location annotations on entities submitted to the validate-entity endpoint can no longer override the location of the request.
github.com/backstage/backstage/releases/tag/v1.56.6

AsyncAPI definition widget no longer resolves external references by default

AffectsAsyncAPI definitions in the definition widget that reference external documents

Whole-document references show a placeholder naming the unloaded document, while references into external documents using a # fragment fail with an error naming the reference. External reference resolution is enabled when the resolvers prop is provided.

Show release-note lines
- 640f025: The AsyncAPI definition widget no longer resolves external references by default. References to whole external documents still render, with a placeholder naming the document that was not loaded; references that point into an external document (using a `#` fragment) fail to render with an error naming the reference. To resolve external references — for example to reach internal schema registries that require authentication — provide the `resolvers` prop to enable external reference resolution.
github.com/backstage/backstage/releases/tag/v1.56.6

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.