Stack Overflow
Stack Overflow

Questions tagged [semantic-release]

semantic-release automates package release workflow.

semantic-release automates package release workflow.

Links

161 questions
12
votes
1 answer

semantic-release breaking-change using ! (exclamation mark)

Can Major version changes (aka Breaking Changes) be handled in semantic-release using the exclamation mark? git commit -m 'feat!: this is breaking, but is not recognized by semantic-release' Conventional Commit guidelines show that breaking changes…
David Cruwys
  • 6,262
  • 12
  • 45
  • 91
12
votes
4 answers

Getting Next tag version using semantic releases

Hi am using semantic release for versioning in my repo. In my Gitlab when i merge my branch with master my tag increases according to the commit and it works fine. Is there any way for me to get the " next tag version " that will come before the…
Origin
  • 1,182
  • 1
  • 10
  • 25
11
votes
1 answer

Changelog handling in semantic-release?

Using semantic-release in our Github workflows. They are setup like this: [ {name: 'main', prerelease: false}, {name: 'staging', prerelease: true}, {name: 'development', prerelease: true} ] Pushes to development are deployed to development…
Moritz Schmitz v. Hülst
  • 3,229
  • 4
  • 36
  • 63
10
votes
2 answers

ERELEASEBRANCHES The release branches are invalid in the `branches` configuration. when I use object

I'm using semantic-release, and I'm trying to create prerelease with configuration module.exports = { branches: [{ name: 'master', prerelease: true }], plugins: [ '@semantic-release/commit-analyzer', …
ridermansb
  • 10,779
  • 24
  • 115
  • 226
7
votes
1 answer

Github: Pushing to protected branches with fine-grained token

I'm using semantic release in a Github repository to create automatic releases on push. The release needs to commit package.json and CHANGELOG.md to my protected branch. I used to provide a personal token from my admin account to allow…
Th3S4mur41
  • 1,930
  • 1
  • 13
  • 28
7
votes
4 answers

How to setup semantic-release without the need for npm?

I have a C# project and would like to add semantic versioning to it. So whenever I push to the main branch I want to create a new release and autogenerate a new version number based on the commit types. I think semantic-release does the job very…
Question3r
  • 2,166
  • 19
  • 100
  • 200
6
votes
0 answers

How do i release previous version of package using semantic-release

I have a npm package which i publish with semantic-release . My master branch is currently on version 2.0.1 , but we recently found a bug for version v1.0.5 and need to fix it by releasing v1.0.6, I checked out from v1.0.5 branch and fixed the bug,…
Akash Salunkhe
  • 2,698
  • 2
  • 16
  • 31
6
votes
1 answer

Many conventional commits of type feat on one feature branch

I've been added to a repo which uses semantic-release to automate bumping up the version of the NPM package. The repo uses the Conventional Commits specification and has a very limited README. If I was to create a feature/ABC-123 branch which…
JS_Dev
  • 427
  • 4
  • 14
5
votes
1 answer

Semantic-Release doesn't create release with BREAKING CHANGE

When I create a commit like this, git commit -m'BREAKING CHANGE: foo bar' and push up semantic-release tells me, [@semantic-release/commit-analyzer] › ℹ Analyzing commit: BREAKING CHANGE: Changes from…
Evan Carroll
  • 78,363
  • 46
  • 261
  • 468
5
votes
1 answer

configure semantic-release to publish pre-release via CLI

My goal is configure semantic-release to create tag from the protected branches like this: npx semantic-release --plugins @semantic-release/commit-analyzer --branches {'name': 'release/super-feature', 'prerelease': true} I'm expecting that tag…
user2738882
  • 1,161
  • 1
  • 20
  • 38
5
votes
2 answers

Gitlab semantic release not using private registry

I'm trying to use semantic-release to publish to a scoped private registry on gitlab but I keep getting error because it's trying to auth against the public registry instead the private one. Here are my settings (with some things…
jfalomir123
  • 71
  • 1
  • 6
5
votes
2 answers

semantic-release not creating new release and changelog not pushed to GitLab

I have the following problem: As soon, as my pipeline starts and a release should be published by semantic-release, nothing happens. Only the correct label is created. My .releaserc looks like this: { "branches": ["master"], "plugins": [ …
Zumpel
  • 82
  • 19
5
votes
1 answer

Missing plugins when running semantic-release in Gitlab CI

I would love to use semantic-release to manage our semantic versioning. For that I tried to integrate it into our Gitlab CI. I followed some examples and provided the necessary environment variables to push code to the repo. When semantic-release…
Chrissi Grilus
  • 1,099
  • 2
  • 9
  • 21
5
votes
0 answers

Maximum number for [major].[minor].[patch]

For @semantic-release, [major].[minor].[patch], what is the maximum number that it can goes to for major, minor, patch? i.e. 999.999.999?
bittersour
  • 937
  • 2
  • 11
  • 32
4
votes
2 answers

Is there a way to create a Gitlab job CI rule that does not run the job when only if one file was updated?

I am trying to write a gitlab ci job rule that does not run when only CHANGELOG.md is committed into the default branch. However, if CHANGELOG.md is updated along with other files in the commit, then run the job. Is this possible? Thank you! The…
J W
  • 107
  • 1
  • 10
1
2 3
…
10 11