feat!: migrate to git-cliff and rewrite gitops workflows#105
Open
swibrow wants to merge 3 commits into
Open
Conversation
github-actions
Bot
added
documentation
…e-tag
Replace semantic-release with git-cliff for automated versioning. This enables
native scoped tags (service_name-v{version}) and monorepo path filtering.
- Rewrite gh-release.yaml to use orhun/git-cliff-action@v4
- Consolidate gh-release-on-main.yaml into gh-release.yaml
- Rewrite gitops-image-tag.yaml to use dnd-it/action-yaml-update@v0
- Add argocd_server passthrough to service-pipeline.yaml
- Add cliff.toml, docs/VERSIONING.md with migration guide
- Rewrite tests for git-cliff, add gitops-image-tag tests
BREAKING CHANGE: gh-release.yaml inputs changed. use_semantic_release,
tag_format, and tag inputs removed. New inputs: service_name, service_path,
cliff_config, metadata_file. gh-release-on-main.yaml removed.
The ref: github.ref_name resolves to '105/merge' in PR context which is not a valid branch name. Letting checkout use the default ref.
Split git-cliff invocation into two conditional steps to avoid --tag-pattern + --bump failing when no matching tags exist yet. First releases skip --tag-pattern and default to version 0.1.0.
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
1 participant
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
gh-release.yaml) — native scoped tags via--tag-pattern, monorepo support via--include-path, removes Node.js dependencygh-release-on-main.yamlintogh-release.yaml— one release workflow,metadata_filesupport portedgitops-image-tag.yamlto usednd-it/action-yaml-update@v0— from ~236 lines yq/sed to ~117 linesargocd_serverpassthrough toservice-pipeline.yaml— forwards toargocd-cli.yamlcliff.toml,docs/VERSIONING.mdwith v3→v4 migration guide, and design docBreaking Changes
gh-release.yamlinputs changed:use_semantic_release,tag_format,tagremoved. New:service_name,service_path,cliff_config,metadata_filegh-release-on-main.yamlremoved (consolidated)gitops-image-tag.yamlinputs simplified to mirroraction-yaml-update@v3are unaffectedTest plan
_test-gh.yaml— dry-run whole-repo, scoped with service_name, PR context forces dry-run_test-gitops-image-tag.yaml— image mode, key mode, input validation rejectionrelease.yamltriggers correctly on merge (creates v4.0.0 via git-cliff)service-pipeline.yamlargocd_server forwarding works withvars.argocd_serverfallback