Skip publishing as npmPublish is [secure] about nx-semantic-release

[TheUnderScorer]

Hey @daniel-clover!

Hmm... this is interesting 😄. In the @semantic-release/npm docs it indicates that npmPublish:

Whether to publish the npm package to the registry. If false the package.json version will still be updated.

but for some reason, the value is obfuscated by your CI and replaced by [secure]. If everything is working as intended, I won't worry about it!

[daniel-clover]

hey @TheUnderScorer !

The problem is that the publishing step is skipped, so the package isn't pushed up to our artifactory.

Any ideas on what I could do? is there any way to force publishing?

Thanks!!!
log (21).txt

[TheUnderScorer]

Try to set this in package.json:

  "publishConfig": {
    "access": "public",
    "registry": "https://registry.npmjs.org/"
  },
  "private": false

Let me know if that helps!

[daniel-clover]

Tried it, but getting the same results :(

log (22).txt

[TheUnderScorer]

Did you set it in the package.json of the project that you are trying to publish?

[TheUnderScorer]

This issue became stale, so I'm going to close it. Feel free to re-open if you still have this problem.