Coder Social home page Coder Social logo

Comments (4)

JayaKrishnaNamburu avatar JayaKrishnaNamburu commented on June 14, 2024 1

Fixed this by adding explicitly like this without npm

"publish": ["@semantic-release/github"]

but not sure why the npmPublish flag is reflecting when the publish is not explicitly defined, and still need to define NPM_TOKEN even if it was being used.

[
  "@semantic-release/npm",
     {
         "npmPublish": false
     }
 ]

from npm.

pvdlg avatar pvdlg commented on June 14, 2024

This question is answered in our FAQ: https://github.com/semantic-release/semantic-release/blob/master/docs/support/FAQ.md#can-i-skip-the-release-to-the-npm-registry

from npm.

JayaKrishnaNamburu avatar JayaKrishnaNamburu commented on June 14, 2024

This question is answered in our FAQ: https://github.com/semantic-release/semantic-release/blob/master/docs/support/FAQ.md#can-i-skip-the-release-to-the-npm-registry

Hi @pvdlg, yes the FAQ says when npmPublish flag is set to false it will not publish to npm but that's not working for me, here are the additional details

"plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/changelog",
    [
      "@semantic-release/npm",
      {
        "npmPublish": false
      }
    ],
    "@semantic-release/github"
  ],
[6:19:24 AM] [semantic-release] [@semantic-release/npm] › ℹ  Published [email protected] on https://registry.npmjs.org/
[6:19:24 AM] [semantic-release] › ✔  Completed step "publish" of plugin "@semantic-release/npm"

Here is the commit

Here is the log from travis

from npm.

JayaKrishnaNamburu avatar JayaKrishnaNamburu commented on June 14, 2024

Fixed this by adding explicitly like this without npm

"publish": ["@semantic-release/github"]

but not sure why the npmPublish flag is reflecting when the publish is not explicitly defined, and still need to define NPM_TOKEN even if it was being used.

[
  "@semantic-release/npm",
     {
         "npmPublish": false
     }
 ]

When i explicitly define only github in the publish step only then it is skipping the process of publishing to npm. Do the docs need some update ? because if so i will be happy to update them and the assets is also not reflecting when it is configured as it is defined in docs --> https://github.com/semantic-release/github#usage 🤔

from npm.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.