feat: Woodpecker-Plugin bump (Entwurf)

Setzt Version und Tag für den gepushten Branch wie bump-version, dazu
hotfix/* -> beta, Bump nur des auslösenden Commits, [skip ci] im
Bump-Commit. Nutzer und Autor oumta-ci, Secret oumta_ci_token
(oumta-deploy docs/zugaenge.md). plugins.yaml baut beide Plugins.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
tuandClaude Opus 5.5 committed 2026-10-30 17:35:17 +01:00
1 parent d071358196
commit 14e760b6eb
4 files changed
+283 -3

No files matched your search

+35 -1
View File
@@ -166,5 +166,39 @@ steps:
registry_password:
from_secret: registry_password
deploy_token:
from_secret: oumta_deploy_token
from_secret: oumta_ci_token
```
### bump
Sets the version for the pushed branch in `package.json`, commits it as `update version: vX [skip ci]`, tags it and pushes branch and tag. The tag event then starts the build; `[skip ci]` only suppresses push and pull_request events.
- `main`: release from the commit message (`release/x.y[.z]`, `hotfix/x.y.z`), otherwise a patch bump
- `release/*`, `hotfix/*`: next `vX.Y.Z-beta.N`
- any other branch: `vX.Y.Z-dev.<UTC timestamp>`; the release line comes from `release_line`, the newest ancestor `release/*` branch, or `package.json`
Only the commit that triggered the pipeline is bumped; if the branch moved on, the step exits without a bump and the newer pipeline takes over.
Settings:
- `git_token` (required): token with write access to the repo (`oumta_ci_token`)
- `git_user`: default `oumta-ci`
- `release_line`: optional, `<major>.<minor>[.<patch>]`
- `author_name`, `author_email`: default `oumta-ci`, `oumta-ci@noreply.git.uesome.de`
- `remote`: default `CI_REPO_CLONE_URL`
Example:
```yaml
when:
- event: push
branch: [develop, 'feature/**', 'release/**', 'hotfix/**']
- event: manual
steps:
- name: bump
image: git.uesome.de/actions/ci-cd/bump:v1.0.0
settings:
git_token:
from_secret: oumta_ci_token
```