Repository path validation for scaffolder actions
Affectsscaffolder setups using the
gitlab:repo:push, publish:gitlab:merge-request or publish:github:pull-request actionsAbsolute paths and paths containing .. segments are rejected in targetPath, and in filesToDelete for publish:github:pull-request, keeping changes inside the intended repository subdirectory.
Show release-note lines
- 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.github.com/backstage/backstage/releases/tag/v1.54.12