Skip to content

ci: release with the shared semver-version and github-release workflows - #55

Merged
vramperez merged 2 commits into
masterfrom
shared-release-workflows
Nov 10, 2026
Merged

vramperez merged 2 commits into
masterfrom
shared-release-workflows

Conversation

@vramperez

Copy link
Copy Markdown
Collaborator

Summary

The pre-release read the semver label from the event that started the run. A pull request opened by a bot gets its label right after it is opened, so every bot pull request failed in Generate version, and re-running it did not help. The versions are now worked out and published with the reusable workflows of FIWARE/github-workflows (v1.2.0):

  • Pre-release: semver-version.yml reads the label when the job runs and gives X.Y.Z-PRE-<number>; github-release.yml publishes it, replacing the one of the previous push, as marvinpinto/action-automatic-releases (archived since 2024) did. The table of contents is updated in a job of its own, as before. Runs of the same pull request no longer overlap.
  • Release: the version comes from the semver label of the merged pull request, and github-release.yml publishes it. The repository so far only published 1.0.0-PRE-<n> pre-releases and never a release; from now on each merge publishes X.Y.Z, starting from the 1.0.0 tag created for it. Releases run one after the other. The documentation is still updated on every push, independently of the version.
  • (decentralized-iam) The manual run keeps its bump_level input, now used as the bump of a commit that no labelled pull request carries; it had no effect before.
  • (odrl-authorization) A manual run releases the version it is given, as before.

zwaldowski/match-label-action, zwaldowski/semver-release-action, actions-ecosystem/action-get-merged-pull-request and marvinpinto/action-automatic-releases are no longer used.

Not a breaking change for the charts: their versions and releases are unchanged.

Testing

  • This pull request's own pre-release is published as 1.0.1-PRE-<number> and replaced on the next push.
  • actionlint on the changed workflows.

vramperez and others added 2 commits November 10, 2026 13:00
The pre-release read the semver label from the event that started the run. A pull request opened by a bot gets its label right after it is opened, so its pre-release always failed, and re-running it did not help. semver-version.yml of FIWARE/github-workflows reads the label when the job runs, and github-release.yml publishes the X.Y.Z-PRE-<number> pre-release, replacing the one of the previous push, as marvinpinto/action-automatic-releases did; that action is archived. The table of contents is updated in a job of its own, as before. Runs of the same pull request no longer overlap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The release version is worked out by semver-version.yml of FIWARE/github-workflows, from the semver label of the merged pull request, and published by its github-release.yml, which replaces the archived marvinpinto/action-automatic-releases. Releases run one after the other, so two merges in a row do not compute the same version. The documentation is updated independently of the version, on every push, as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vramperez
vramperez merged commit f476ed3 into master Nov 10, 2026
12 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants