4

[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.

On .releaserc.js

module.exports = {
  branch: 'development',
Werner Henze
  • 16,404
  • 12
  • 44
  • 69
Андрей СТ
  • 41
  • 1
  • 2

1 Answers1

5

The correct option is branches. See https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#branches

Pierre Vanduynslager
  • 811
  • 7
  • 7