The semantic-release and electron-builder are both publishing a Github Release.
I want to combine them, so semantic-release will be responsible for the release version and CHANGELOG, but the electron-builder will be responsible for the publishing…
I'm trying to create prereleases to go with my normal releases.
when I do a prepatch merge to my release branch I would like my version to change from
1.0.0
to
1.0.1-rc-0
I know i can use prerelease like below, but this only incriments the last…
I am trying to integrate semantic-release into my Node CI/CD workflow. I have tried following the documentation and tutorials but I am clearly missing something. The testing step passes, but the publish step fails at "Run npx semantic release".
This…
I created a minimal reproduction which is a monorepo contains only one workspace in `./package' dir
both root and package (the workspace) have exactly the same release.config.js file except that package extends semantic-release-monorepo.
both of…
Here is the error log message:
[3:40:55 PM] [semantic-release] › ✖ The command "git push --dry-run
--no-verify https://gitlab-ci-token:[secure]@[repository-url].git
HEAD:main" failed with the error message remote: You are not allowed
to upload…
I have a C# solution containing a single project and multiple libraries using .Net 6. I'm using conventional commits (commitlint with husky) and want to use semantic-release to deploy the latest build as a ZIP file on Github based on the commit…
I am trying to publish a package from my app.
I get this error at the publish step:
[2:28:46 PM] [semantic-release] › ℹ Running semantic-release version 18.0.0
[2:28:46 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from…
I have two branches, branch-A(Which has tags 1.0.0, 1.1.0, 1.1.1, 1.1.2), branch-B (created on top of branch-A). We are doing the development in both the branches parallelly.
After branch-B was created I did some more releases from branch-A…
I have a case where I need to include the commit in the semantic-release/commit-analyzer but not in semantic-release/release-notes-generator. Is it possible to do this in Github actions semantic release?
I'm using the semantic-release package which runs on my CI to release my library onto npm through my Github repo.
Recently, I have a breaking change that I have forgotten to add the breaking change text into my commit message before merging. So…
I am very new to semantic release so not sure I can exec multiple @semantic-release/exec at a time in a single .releaserc file.
Please let me know if this is feasible, if yes then what is my mistake.
I am getting error:
[7:30:34 AM]…
I already set the varaible,but it seems not work.
sementic log shows its was using @semantic-release/github,but actually my repo is in the gitlab, is that reason?By the way i have already install the @semantic-release/gitlab…
I have a private npm package that is currently published to npm. The maintainer before me did not consider automated versioning, and the version is 1.0.58.
I have installed semantic-release and a small GitHub app that can be found here:…
how should semantic release be configured to produce a unique semantic versioning for each branch (set all branches as release branch).
that is, assume a random branch name - how do semantic release should be configured to make the random branch as…
I would like to add a check to semantic-release to only allow it to publish minor and patch releases. If it detects the need to perform a new major release, I want the process to be aborted and fail (instead of proceeding to perform the release).…