New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development/development strategy #188
Comments
👍 We could keep the |
We can also use |
I agree with you @asbjornu. Better to have a spec to reference than something special. So we'll end up with something like this then? 👇 "branches": [
"+([0-9])?(.{+([0-9]),x}).x",
"main",
"release/*",
{
"name": "develop",
"prerelease": true
}
] Who wants to do it? |
Having |
Actually, after looking at this a second time, I don't know how I thought To further explain the configuration I proposed above. Also, the Developers would create a pull request with Better example{
"branches": [
"+([0-9])?(.{+([0-9]),x}).x",
"main",
{
"name": "next",
"prerelease": "rc"
},
{
"name": "develop",
"prerelease": true
}
]
PS: To support I don't know how |
In Git Flow |
I'll create a quick pull request with documentation, so we can review the changes there. 👍 |
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
We talked about changing how we develop and deploy, in short, these are the changes we talked about:
master
-->main
(meant for stable releases)alpha
-->develop
(meant for development)develop
branch will have canary releases, meaning it will release a prerelease version with every merge that contains at least one commit message annotated according to Conventional Commit.We have to remember to change the configuration of Semantic Release with this change, this file:
swedbank-pay-sdk-js/.releaserc.json
Lines 30 to 38 in fc5ab94
The
next
branch will be used in the future for next mayor releases.cc: @asbjornu @NullableInt
The text was updated successfully, but these errors were encountered: