-
Notifications
You must be signed in to change notification settings - Fork 265
Gitlab flow help #1439
Copy link
Copy link
Open
Labels
Description
Question
I really like the tool but I struggle to make it work for my case.
I have a Gitlab flow setup with main, staging and production branches.
From time-to-time main is merged into staging and staging is merged to production.
I run semantic-release on all three branches
My flow is:
- I create a couple of "feat: ..." commits in
main. They are correctly tagged as1.0.0-dev.1and1.0.0-dev.2 - I then merge
maintostaging. The merge commit is correctly tagged as1.0.0-rc.1 - I merge
stagingtoproduction. The merge commit in production is correctly tagged as1.0.0 - I create a new "feat: ..." commit in
main. It receives a1.0.0-dev.3tag instead of1.1.0-dev.1 tag
Am I doing something wrong or this case is not supported and there is nothing I can do to make it work correctly?
Would appreciate any insights. Thanks!
Configuration
Semantic Release Configuration
[semantic_release.branches.main]
match = "main"
prerelease_token = "dev"
prerelease = true
[semantic_release.branches.staging]
match = "staging"
prerelease_token = "rc"
prerelease = true
[semantic_release.branches.production]
match = "production"
prerelease = falseAdditional context
I run semantic-release -c releaserc.toml -vv version --no-commit --no-changelog --no-vcs-release on main
I run semantic-release -c releaserc.toml -vv version --no-commit --no-changelog on staging and production
I do merges with --no-ff
git log --oneline --decorate --graph --all -n 50
* b04fbea (tag: v1.0.0-dev.3, origin/main, origin/HEAD, main) feat: feature 3
| * d155f0f (HEAD -> production, tag: v1.0.0, origin/production) Merge branch 'staging' into production
| |\
| | * 4ecd51f (tag: v1.0.0-rc.1, origin/staging, staging) Merge branch 'main' into staging
| | |\
| |_|/
|/| |
* | | 19ab5f9 (tag: v1.0.0-dev.2) feat: add feature 2
* | | e3e60be (tag: v1.0.0-dev.1) feat: feature 1
Reactions are currently unavailable