Repository navigation
ci: release with the shared semver-version and github-release workflows - #55
Merged
Merged
Conversation
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>
Mortega5
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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):semver-version.ymlreads the label when the job runs and givesX.Y.Z-PRE-<number>;github-release.ymlpublishes it, replacing the one of the previous push, asmarvinpinto/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.github-release.ymlpublishes it. The repository so far only published1.0.0-PRE-<n>pre-releases and never a release; from now on each merge publishesX.Y.Z, starting from the1.0.0tag created for it. Releases run one after the other. The documentation is still updated on every push, independently of the version.bump_levelinput, now used as the bump of a commit that no labelled pull request carries; it had no effect before.zwaldowski/match-label-action,zwaldowski/semver-release-action,actions-ecosystem/action-get-merged-pull-requestandmarvinpinto/action-automatic-releasesare no longer used.Not a breaking change for the charts: their versions and releases are unchanged.
Testing
1.0.1-PRE-<number>and replaced on the next push.