semantic-release/npm

Issues

• Failed step "prepare" of plugin "@semantic-release/npm" due to reading malformed path

  #773 opened 10 months ago by joshunrau
  14

• Why support of legacy auth was dropped?

  #598 opened 2 years ago by Tri0L
  3

• Feature request: check permission to publish in verify step (if it's even possible)

  #848 opened 6 months ago by jedwards1211
  1

• K

  #846 opened 6 months ago by SHAHAD-way
  0

• [Question] monorepo project

  #829 opened 8 months ago by nikolicjakov
  1

• semantic-release/npm forced npm version in scripts

  #524 opened 2 years ago by ghmeier
  3

• npm ERR! log.http is not a function

  #809 opened 9 months ago by mcarvin8
  4

• Cannot set properties of null (setting 'peer')

  #807 opened 9 months ago by seahindeniz
  4

• [bug] ignores pkgRoot when used with semantic-release-monorepo

  #511 opened 2 years ago by its-dibo
  2

• pkgRoot property not working

  #601 opened 2 years ago by paulorenanmelo
  1

• ERR_INVALID_AUTH triggered by semantic-release npm despite not having this field set in checkout directory

  #777 opened 9 months ago by cdaringe
  11

• account for deprecation of `_auth` in existing `.npmrc` files

  #792 opened 9 months ago by travi
  0

• align approach for concatenating `.npmrc` files to better align with default npm behavior

  #791 opened 9 months ago by travi
  0

• improve auth token resolution

  #790 opened 9 months ago by travi
  0

• Array format/style is being changed

  #789 opened 9 months ago by Th3S4mur41
  3

• Security Issue with out of date tar@6.2.0 found with SNYK

  #784 opened 10 months ago by jebarpg
  3

• semantic-release seems publishing twice and causing error.

  #779 opened 10 months ago by ianzone
  1

• NPM Audit Signatures issue on 11.0.3

  #763 opened a year ago by nicholasgriffintn
  2

• Support for custom package.json properties to write changelist entries

  #761 opened a year ago by ggrafhalfbrick
  0

• CVE-2023-42282

  #756 opened a year ago by bpneal
  1

• Update a package.json in a sub folder

  #750 opened a year ago by Johannes-Schiel
  0

• Publishing failed since update from npm@10.2.4 to npm@10.2.5 with files mentioned in .gitignore

  #725 opened a year ago by darlenya
  6

• error on publishing

  #654 opened 2 years ago by sivaselvimahalingam
  1

• Command failed with exit code 1: npm version 0.22.2 --userconfig

  #651 opened 2 years ago by CalicoNino
  2

• Set --no-workspaces with npm version

  #639 opened 2 years ago by wilbert-abreu
  2

• npm whoami failing

  #612 opened 2 years ago by kpruden
  3

• `package.json` version not updated, despite correct plugin ordering

  #615 opened 2 years ago by jimbojw
  1

• Add support for npm v9

  #530 opened 2 years ago by Mitchell-Mulder
  7

• fix vulnerability with http-cache-semantics <4.1.0

  #574 opened 2 years ago by ydekel6
  4

• Provenance support not working?

  #605 opened 2 years ago by seebeen
  1

• npm publish fails / `npm publish <folder>` publishes from cwd folder

  #504 opened 3 years ago by unlight
  14

• Use clean-publish

  #546 opened 2 years ago by BondarenkoAlex
  0

• a `Cannot read properties of null (reading 'matches'` error when using multi-semantic-release

  #540 opened 2 years ago by arvinxx
  8

• npm publish looks for package.json at disk root

  #536 opened 2 years ago by euginetwr
  3

• Incompatible with Yarn (Berry)

  #539 opened 2 years ago by mklueh
  1

• `prepack` run twice when set `tarballDir`

  #535 opened 2 years ago by atian25
  1

• Why is `npm version` used to set the version?

  #526 opened 2 years ago by oliversalzburg
  1

• Provide a better error message in case of an E400 bad request without further explanation from npm

  #519 opened 2 years ago by gr2m
  0

• You cannot publish over the previously published versions

  #518 opened 2 years ago by oliveirarafa
  0

• HIGH SEVERITY security problem CVE-2021-3795 (semver-regex and find-versions)

  #517 opened 2 years ago by pierluigilenoci
  3

• `npm publish` failing: `The "path" argument must be of type string. Received undefined`

  #508 opened 2 years ago by RebeccaStevens
  1

• no-workspaces-update option

  #495 opened 2 years ago by johngeorgewright
  3

• Lifetime scripts do not seem to execute

  #507 opened 3 years ago by MichaelBrunn3r
  3

• Issues getting postversion to work

  #506 opened 3 years ago by MichaelBrunn3r
  0

• Sign published packages with sigstore

  #505 opened 3 years ago by JamieMagee
  1

• Version doesn't increment in `package.json` of yarn workspace, because of `EUNSUPPORTEDPROTOCOL`

  #500 opened 3 years ago by adrienjoly
  1

• i have some qustion

  #499 opened 3 years ago by astronautchen
  0

• Upgrade peer dependency semantic-release to version 19.0.3 or later to fix known vulnerability

  #498 opened 3 years ago by ocofaigh
  0

• fails to find pkgDir in some versions

  #492 opened 3 years ago by its-dibo
  0

• Clarification on the proper way to change settings when doing a fork

  #483 opened 3 years ago by sneko
  0