# Backstage v1.56.6

2026-11-17 · [Original release notes](https://github.com/backstage/backstage/releases/tag/v1.56.6) · [Full summary](https://ratatosk.io/en/releases/backstage/v1.56.6)

Security 5 · Breaking changes 2

## Check before upgrading

### Upgrade guide

- **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)

## Security (5)

### Kubernetes proxy stops forwarding caller headers

- Affects: Kubernetes 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.

> - 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.

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

- Affects: catalog 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.

> - 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.

### Fetch-action credential host check fixed

- Affects: setups with `scaffolder.requireScmUserCredentials` enabled
- Additional action: `scaffolder.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.

> - 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.

### Scaffolder actions reject paths outside the target repository

- Affects: setups 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.

> - 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.

### GitLab scaffolder actions reject unsafe paths

- Affects: GitLab 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.

> ## @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.

## Breaking changes (2)

### `validate-entity` request location takes precedence over entity annotations

- Affects: setups submitting entities with location annotations to the `validate-entity` endpoint

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

> - e6e35ab: Location annotations on entities submitted to the validate-entity endpoint can no longer override the location of the request.

### AsyncAPI definition widget no longer resolves external references by default

- Affects: AsyncAPI 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.

> - 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.

---

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