semantic-release/semantic-release

📦🚀Fully automated version management and package publishing

Christopher Hiller

@boneskull

Hi, where can I find the “default” configuration? I ran semantic-release-cli setup, but it didn’t create a configuration file. I’m looking to add a plugin but don’t want to foul things up.

Pierre Vanduynslager

@pvdlg

In the documentation: https://github.com/semantic-release/semantic-release#documentation

Pierre Vanduynslager

@pvdlg

That’s not supported. See semantic-release/semantic-release#193

Christopher Hiller

@boneskull

@pvdlg were you replying to me? I don’t see a default configuration… it’s a little difficult to navigate the documentation there

Pierre Vanduynslager

@pvdlg

You have all the default options there: https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/configuration.md#options

Richard Všianský

@rvsia

Hello everyone, is there any option how to change semantic-release bot comments' content? We would like to include link to demo in them. Thanks!

Pierre Vanduynslager

@pvdlg

Which comments exactly?

Richard Všianský

@rvsia

@pvdlg Comments in PRs when the PR is included in release of a new version

This PR is included in version 0.1.0 🎉

The release is available on... and so on

Pierre Vanduynslager

@pvdlg

https://github.com/semantic-release/github#successcomment

Richard Všianský

@rvsia

:+1: Great, thank you!

Richard Všianský

@rvsia

Hello, I'm trying to get custom successComment working. What am I doing wrong? Thank you! :tada:

"release": {
    "prepare": [
      "@semantic-release/npm",
      {
        "path": "@semantic-release/git",
        "assets": [
          "package.json"
        ],
        "message": "Release of new version: ${nextRelease.version} <no> [skip ci]",
        "successComment": ":tada: This ${issue.pull_request ? 'PR is included' : 'issue has been resolved'} in version ${nextRelease.version} :tada:\n\nThe release is available on \n\n- [GitHub release](<github_release_url>)\n\n- [npm package (@latest dist-tag)](<npm_release_url>)\n\nDemo can be found [here](http://data-driven-forms.surge.sh/)!"
      }
    ]
  },

Kai Schwarz

@papakai

Hey guys!
I am currently working on a PERL Module and I also want to automate the release process there using travis ci and semantic-release
Does anyone know if there's an available semantic-release plugin for perl? So for publishing on PAUSE/CPAN?
TIA!

Pierre Vanduynslager

@pvdlg

@rvsia You set the successComment in the @semantic-release/git option which doesn’t have this option. I think you are looking for the option in the @semantic-release/github plugin. Please read the docs of the plugins you are using.

Pierre Vanduynslager

@pvdlg

We are moving this community to Spectrum. Please join https://spectrum.chat/semantic-release !

Frank Lemanschik

@frank-dspeed

@pvdlg please consider joining https://github.com/nodejs/package-maintenance we founded it to discusse general package maintance standards

@reconbot you too please if you read that

Clite Tailor

@clitetailor

what are the differences between improvement and refactor commit message in conventional commit? :/

Marc Guilera

@marcguilera

hey is it possible to pass complex arguments to the CLI (arrays for plugins like using the JSON)

Dimitri KOPRIWA

@kopax

I am trying to use semantic-release on gitlab-ci. Why is the release job on master branch showing: (HEAD detached from 15a789b3)

instead of being on master?

Dimitri KOPRIWA

@kopax

is there a way with @semantic-release/exec to know the next version in the prepare step?

Neil Kalman

@Thatkookooguy

hi! anyone here? I'm trying to get some help troubleshooting something with semantic-release

Dimitri KOPRIWA

@kopax

Hi, I am lost, I am trying to figure out why the master..dev are different but it says there's nothing to merge

Rach

@rach_1412_twitter

I added semantic-release github-action to a repo and for the first run say I used npm install so as to sync package.json and package-lock.json file. However from the second run I just like to use npm ci as part of the CI pipeline. But I am getting errors such as npm WARN prepare removing existing node_modules/ before installation
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm ERR!
npm ERR!
npm ERR! Missing: is-installed-globally@^0.3.1
npm ERR! Missing: karma@^4.4.1
npm ERR! Missing: @semantic-release/git@^7.0.18
npm ERR! Missing: cz-conventional-changelog@^3.0.2
npm ERR! Missing: git-cz@^3.3.0
npm ERR! Missing: http-server@^0.11.1
npm ERR! Missing: last-release-git@0.0.3
npm ERR! Missing: semantic-release@^15.13.30
npm ERR!

Unless I run both npm i && npm ci I keep getting the above errors. I would appreciate any help on this!

Hasitha Shan

@hh_shan_twitter

Hi, is there a way to release using the current version in package json through the next branch?

my last release from the next branch is 2.4.0@next, I merged my beta branch to the next branch, which now the version reads 2.5.0-beta.3, and when I try to release from the next branch it tries to release it as v3.0.0 instead of v 2.5.0..any idea how to fix this? or is this the usual behaviour?

@pvdlg

Thanks alot :)

Dimitri KOPRIWA

@kopax

Merry Christmas IRC friends. Lot'S of success and less bugs to all. and sorry for amsg :)!

Dimitri KOPRIWA

@kopax

Hello, I would like to update the version number as well in server/package.json while publishing with semantic-release, how can I do using @semantic-release/exec, just the publish step is having the version while I need to prepare it first.

anragen

@anragen

Frank Lemanschik

@frank-dspeed

i would say incrementing the version number is the last step

many people even do that via a additional commit

anragen

@anragen

When i run semantic-release --no-ci on branch development a get This test run was triggered on the branch development, while semantic-release is configured to only publish from master, therefore a new version won’t be published.

how can i fix semantic-release to trigger on the branch development?

Frank Lemanschik

@frank-dspeed

fix semantic realease requires a bug first

anragen

@anragen

in .releaserc.js i have module.exports = {
branch: 'development',

Frank Lemanschik

@frank-dspeed

i think you should review your whole setup

maybe you need to do more then that

you need to understand your release process in any way there is no short route for that

anragen

@anragen

git show -s HEAD (HEAD -> development, origin/development)

all output is

semantic-release --no-ci

[16:07:15] [semantic-release] › ℹ Running semantic-release version 17.0.4
[16:07:18] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[16:07:19] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/git"
[16:07:19] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[16:07:19] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/changelog"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/git"
[16:07:19] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[16:07:20] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/gitlab"
[16:07:20] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/npm"
[16:07:20] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[16:07:27] [semantic-release] › ℹ This test run was triggered on the branch development, while semantic-release is configured to only publish from master, therefore a new version won’t be published.

https://paste.ofcode.org/iNNA7sD3Xb4KvPKt4Up3tg .releaserc.js file

@frank-dspeed i mean configure

Brenda

@thehme

hi all, when someone squash merged in GitLab, if the custom message is not created in the format type(subject): description, then the semantic-release fails to release a new version. Is there a recommendation somewhere on what settings should be in the CI?

Brenda

@thehme

@thehme for now, we are just telling team members to add the custom message, but this is prone to error since people are so used to squash merging in GitLab, without adding a message, let alone a formatted message.

Where communities thrive

People

Repo info

Activity