Repository navigation
Add a semver-version workflow, helm-docs in chart-pr and OCI push retries - #1
Merged
Merged
Conversation
semver-version.yml works out the version a pull request releases from its semver label: X.Y.Z-PRE-<number> on the pull request, X.Y.Z on the push of its merge. It replaces the per-repository label check and version jobs of application repositories. next-version.sh takes the tag prefix, for repositories whose tags are plain X.Y.Z. chart-pr.yml can regenerate the charts' documentation with helm-docs after the bump, and publish-oci.sh retries a push that fails, as quay answers 502 now and then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The repository moved to the FIWARE organization. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds what the FIWARE application repositories and helm-charts need to move onto these workflows, and points the examples to the repository's new home in the FIWARE organization.
semver-version.yml(new): works out the version from the semver label of the pull request. On a pull request it requires exactly one ofmajor,minor,patch(commenting when it is missing) and returnsX.Y.Z-PRE-<number>. On a push to the main branch it reads the label of the merged pull request and returnsX.Y.Z. It replaces thecheck.ymlandgenerate-versionjobs that fdsc-edc, contract-management and consent-facade copy from one another, built onzwaldowski/*andactions-ecosystem/action-get-merged-pull-request.next-version.sh:TAG_PREFIX(defaultv, unchanged behaviour), for repositories whose tags are plain1.2.3.chart-pr.yml: optionalhelm-docs-version, which regenerates the README of the charts the pull request changes after the bump. Only those charts: regenerating a stale README of another chart would change that chart without a new version, whichchart-release.ymlrefuses.bump-chart-versions.shnow also outputs the changed charts (changed=).publish-oci.sh: retries a failedhelm push(3 attempts by default). quay.io answered 502 twice on 2026-10-28, and the script stopped at the first chart that failed.FIWARE/github-workflows.test.ymlalso runssemver-version.ymlon its own pull requests.Checks:
shellcheck scripts/*.sh,bats tests(41 tests) andactionlintpass. Dry run of the version on the callers' tags: fdsc-edc 1.8.6, contract-management 3.4.2, consent-facade 0.4.3 for apatch.Once released (v1.1.0), the callers switch from
SEAMWARE/github-workflowstoFIWARE/github-workflows: data-space-connector, decentralized-iam, vc-authentication and odrl-authorization, plus helm-charts, fdsc-edc, contract-management and consent-facade, which move onto these workflows.🤖 Generated with Claude Code