ci: migrate to ci-workflows@v6 config file - #25
Merged
Conversation
Per-project options move from with: blocks to .fluence-ci.yml per ci-workflows v6. Wrappers become byte-identical to the gems family canonical set (fluence-eu/fluence-gateway-client#62): pinned @v6, no with:, comments deduplicated from the ci-workflows README, release trigger on the generic lib/**/version.rb glob, publish without gem_name (v6 publishes every .gem release asset).
🛡️ Documentation Quality: 100.0% (0.0%)
✅ Documentation quality above threshold. |
📊 Code Quality Report
✅ No new code-quality findings. 🔍 All 85 reek smells on this PR
📊 Flog complexity breakdown📊 Flay duplication breakdown |
🛡️ Coverage Report: 100.0% (0.0%)
✅ All changes are tested. |
🛡️ RuboCop: 0 offenses (0)
✅ No RuboCop offenses. |
Canonical fix (fluence-gateway-client follow-up): all four PR gates forward FLUENCE_RELEASE_BOT_PRIVATE_KEY so release PRs skip them.
The key is optional and would only skip an advisory check on release PRs — not worth widening the secret surface. Canonical stays without.
Arbitrage final : les 4 gates PR forwardent la même clé optionnelle (skip des PRs de release), codequality-pr compris — cf. fluence-eu/fluence-gateway-client#64.
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.
Quoi
Migration vers ci-workflows v6, sur le modèle de fluence-gateway-client#62 : les options par projet passent des
with:au.fluence-ci.yml, et les wrappers deviennent byte-identiques aux templates du groupe gems (pin@v6, commentaires dédupliqués du README ci-workflows).Changements notables (au-delà du mécanique)
release.yml: le trigger passe delib/<gem>/version.rbau glob génériquelib/**/version.rb— le gate bot-author du reusable fait le tri.publish.yml:gem_namesupprimé — le reusable v6 publie tous les assets.gemde la release.prepare-release.yml/release.yml:gem_specsdéménage dans.fluence-ci.yml.codequality-pr.yml: forwardeFLUENCE_RELEASE_BOT_PRIVATE_KEYcomme les 3 autres gates (arbitrage : même sémantique de skip des PRs de release sur les 4 gates — fluence-gateway-client#64).codequality.paths: libdéménage dans.fluence-ci.yml.rubocop-pr.yml: réalignement d'espaces uniquement.