Repository navigation
ci: work out and publish the versions with the shared workflows - #138
Merged
Merged
Conversation
The pre-release and the release worked out the version with zwaldowski/match-label-action, zwaldowski/semver-release-action and actions-ecosystem/action-get-merged-pull-request, and published it, with the binaries, with marvinpinto/action-automatic-releases, which is archived. They now use semver-version.yml and github-release.yml of FIWARE/github-workflows: the label is read when the job runs, the pre-release of a pull request is replaced on every push, and a release is never replaced. A version given to the release workflow is still used as it is. A push to main whose pull request has no semver label now fails the release, as in the other FIWARE repositories, instead of being skipped silently. check.yml, which only checked the label, is removed: the pre-release checks it and asks for it. Unlike pull_request_target, it cannot comment on a pull request from a fork, but the check still fails there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vramperez
added
the
patch
Mortega5
approved these changes
Nov 11, 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 version of the pre-release and the release was worked out with
zwaldowski/match-label-action,zwaldowski/semver-release-actionandactions-ecosystem/action-get-merged-pull-request, and published, with the binaries, withmarvinpinto/action-automatic-releases, archived since 2024. They now use the reusable workflows of FIWARE/github-workflows (v1.2.1), as the other FIWARE repositories do:semver-version.yml): the semver label is read when the job runs. A version given to the release workflow is still used as it is.github-release.yml), withLICENSEand thevcverifier-*binaries attached as before: the pre-release of a pull request is replaced on every push, a release is never replaced, and the notes start from the previous release.check.yml, which only checked the label, is removed: the pre-release checks it and asks for it. On a pull request from a fork it can no longer comment, but the check still fails.Behaviour change
A push to
mainwhose pull request has no semver label now fails the release, as in the other FIWARE repositories, instead of skipping it silently. A change that is not meant to be released still needs a label (patch).With today's tags, a
patchpull request still gives6.31.1.Testing
6.31.1-PRE-<number>, with the binaries, and replaced on the next push.🤖 Generated with Claude Code