Provide `semantic-release` configuration to respect `main` branch

[latipun7]

Provide `semantic-release` configuration to respect `main` branch

[Nikaple]

Yeah definitely. I knew this workflow wasn't the best when I set it up, and even made a few mistakes with releases. Your PR will be very helpful to the project, I'm really appreciated for it!

[Nikaple]

It's actually correct this time, because the release was merged from alpha to next (which triggers the release of v2.0.1), and then from next to main (which will trigger v2.0.1 again but that will result in an npm error). So I guess we can delete the next branch, use only one major version, and use @latipun7/releaserc for semantic-release on the main branch?

[latipun7]

So I guess we can delete the next branch, use only one major version

You don't need to delete it with my config. I believe it will release in the main branch as latest dist-tag in npm, but if you release in the next branch, this time the user needs to install your package with next dist-tag, so npm install nest-typed-config@next

To better understand the workflow, here's some nice explanations with examples.
The only difference with my config is, the latest dist-tag configured with the main branch, while next dist-tag is only configured with next branch only. While pre-release dist-tag for alpha & beta is configured in the branch alpha & beta.

and use @latipun7/releaserc for semantic-release on the main branch?

yes, if you agree to use my config, I could make the PR later 😁

[Nikaple]

The only difference with my config is, the latest dist-tag configured with the main branch, while next dist-tag is only configured with next branch only. While pre-release dist-tag for alpha & beta is configured in the branch alpha & beta.

At first the release branch was set to main only, but at some point I need next and alpha releases. Then I returned to semantic-release docs again, and found that the default config was somewhat "ok", so I deleted the release branch config. But I didn't notice that it's master branch not main branch in the default config. It's, just, surprising I think.

[github-actions]

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀