As far as I read the documentation of semantic-release, it does many things in sequence.
It applies the tag in the commit and publish it to the Github releases.
Q: Is it possible to separate those 2 steps somehow?
In 1st stage, I only want to apply…
When running npx semantic-release-cli setup with GitHub Actions for my public repository https://github.com/henrycity/movie-browser-frontend, I got this error
ERR! semantic-release RequestError: Error: Invalid URI…
If there is any changes via merge from branch to master, we need semantic-release to analyse the commit message and increase the release version. We are using Bitbucket scm. The process of how we merge from branch to master, developer create a pull…
Running this command
yarn semantic-release-cli setup
And giving these answers
? What is your npm registry? https://registry.yarnpkg.com/
? Which authentication method is this npm registry using? Token based
? What is your npm username? ...
? What…
I'm using semantic-release to automatically define the next version, update package.json and push to git. However, I'm facing a problem where it stop me from direct pushing to master.
I'm using GitLab.
my release.config.js
module.exports = {
…
We migrated 5 Angular projects into a NX Monorepo, for CI/CD we use Azure DevOps.
Before switching to the monorepo we were using semantic releases, but now this approach would not be so great anymore as there would be just one release at the time…
I am trying to follow GitLab flow with staging and production environments. I also want semantic-release plugin for both environments (with this I also need a branch for every environment so semantic-release could work, right?)
I have successfully…
I started using semantic-release for some projects I have, is there a way to "force" a patch release on a docs: commit?
Why on docs? Because it publishes on npm too and I want to have the latest documentation there.
I also use dependabot to keep my…
I am trying to release a package to npm.
When CircleCI is trying to run semantic-release it throws the following error:
/home/circleci/src/node_modules/semantic-release/node_modules/execa/index.js:18
const env = extendEnv ? {...process.env,…
We're using GitHub Action to automatically publish our application. For this, we call semantic-release in our CI pipeline and then generate the binaries with electron-builder in the next step. We need binaries for MacOS, Windows and Linux. Sadly, we…
I am using semantic-rlease library and here is my release.config.js:
require('dotenv').config();
module.exports = {
branch: 'rel',
dryRun: false,
debug: true,
repositoryUrl: 'https://github.xxx.com/xxx/backend',
githubUrl:…
In my node project - I'm trying to implement semantic-release to generate release notes in the form of the changelogs, bump the project version number.
The same is installed in the project following the below command:
npm i -D semantic-release@next…
We are trying to implement automatic version bumping based on the semver spec... Ideally, we would just merge into master and produce a new version update on the CI.
--------------development branch----
/ …
I have setup a CircleCI job to run semantic-release, but I would like CircleCI to fail when no changes are found. i.e. when semantic-release outputs:
There are no relevant changes, so no new version is released
CircleCi snippet for the runline.
…
I'm implementing a semantic-release plugin but when I applied it to build, it triggers following error.
I can understand that generated configuration for my plugin (gradle-semantic-release-plugin) is bad, but I cannot find why it happened and how I…