releaser-pleaser/docs/reference/gitlab-cicd-component.md
Julian Tölle f1aa1a2ef4
refactor: let updaters define the files they want to run on (#233)
This change reverses the responsibility for which files the updaters are
run on. Now each updater can specify the list of files and wether the
files should be created when they do not exist yet. This simplifies the
handling of each update in releaserpleaser.go, as we can just iterate
over all updaters and call it for each file of that updater.

Also update the flags to allow users to easily define which updaters
should run.
2025-08-23 22:14:34 +02:00

3 KiB

GitLab CI/CD Component

Reference

The CI/CD component is available as $CI_SERVER_FQDN/apricote/releaser-pleaser/run on gitlab.com.

It is being distributed through the CI/CD Catalog: apricote/releaser-pleaser.

Versions

The apricote/releaser-pleaser action is released together with releaser-pleaser and they share the version number.

The component does not support floating tags (e.g. v1) right now (#31). You have to use the full version or commit SHA instead: apricote/releaser-pleaser@v0.4.0.

Inputs

The following inputs are supported by the component.

Input Description Default Example
branch This branch is used as the target for releases. main master
token (required) GitLab access token for creating and updating release PRs $RELEASER_PLEASER_TOKEN
extra-files List of files that are scanned for version references by the generic updater. ""
version/version.go
deploy/deployment.yaml
updaters List of updaters that are run. Default updaters can be removed by specifying them as -name. Multiple updaters should be concatenated with a comma. Default Updaters: changelog,generic "" -generic,packagejson
stage Stage the job runs in. Must exists. build test
needs Other jobs the releaser-pleaser job depends on. []
- validate-foo
- prepare-bar