# Backstage v1.54.12

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

Security 1

## Check before upgrading

### Upgrade guide

- **Upgrade Helper for v1.54.12**
  > Upgrade Helper: [https://backstage.github.io/upgrade-helper/?to=1.54.12](https://backstage.github.io/upgrade-helper/?to=1.54.12)

## Security (1)

### Repository path validation for scaffolder actions

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

Absolute paths and paths containing `..` segments are rejected in `targetPath`, and in `filesToDelete` for `publish:github:pull-request`, keeping changes inside the intended repository subdirectory.

> - 40f50dd: 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.
> - 40f50dd: 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.

---

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