JS-DevTools/npm-publish

Issues

• Support for snapshot versions

  #202 opened 5 months ago by rrigoni
  3

• Not working on Windows with latest version of Node.js

  #198 opened 5 months ago by mcous
  0

• Possibly provide more of the built-in npm "dry run" output

  #184 opened 8 months ago by forevermatt
  4

• Unable to publish package

  #182 opened 8 months ago by LoeiFy
  1

• InvalidPackageVersionError: Package version must be a string, got "undefined"

  #160 opened a year ago by michaelnlindsay
  6

• `v`-prefix in `package.json` version causes false negative during version comparison

  #139 opened a year ago by scraly
  2

• Publish failure message is masked by `TypeError: _b.toUpperCase is not a function`

  #119 opened a year ago by andybalaam
  6

• I Don't Get `type` When Publishing To Private Repos

  #128 opened a year ago by johnnyshankman
  1

• Support Github App

  #116 opened a year ago by matanbaruch
  2

• Unable to publish package for the first time

  #117 opened a year ago by abhishiv
  3

• Support NPM Package Provenance

  #88 opened 2 years ago by sachaw
  10

• Version check fails if `latest` tag does not exist in registry

  #89 opened 2 years ago by hardillb
  5

• Question: `rc` version release

  #87 opened 2 years ago by danpacho
  2

• Failed to publish

  #78 opened 2 years ago by alexbeletsky
  2

• Extend package argument to handle directory, file, or archive

  #81 opened 2 years ago by razor-x
  0

• Configure publish directory

  #59 opened 2 years ago by ekabolotina
  1

• Chore: release version 2

  #74 opened 2 years ago by mcous
  1

• Specify `ignore-scripts` when publishing

  #47 opened 2 years ago by jamietanna
  0

• working-directory not respected

  #51 opened 2 years ago by gravitypersists
  1

• If tag isn't specified, fall back to publishConfig

  #36 opened 2 years ago by rikoe
  0

• Checking for npm package existence should ignore tag and check against all versions

  #35 opened 2 years ago by rikoe
  0

• Chore: rename `master` branch to `main`

  #71 opened 2 years ago by mcous
  0

• `check-version` is slightly different from what I'd expect/want

  #42 opened 2 years ago by rivertam
  1

• Custom registry URL is truncated for token config

  #46 opened 2 years ago by hermann-noll
  1

• Publish to a private registry authentication fails and work around

  #54 opened 2 years ago by Dreamystify
  1

• Action does not publish non-scoped package to NPM

  #53 opened 2 years ago by WillsterJohnson
  2

• Upgrade Action to use node 16 instead of node 12

  #61 opened 2 years ago by ericcornelissen
  1

• Deprecation warning for 'set-output'

  #67 opened 2 years ago by dht
  2

• "Dependencies" badge doesn't work anymore

  #49 opened 2 years ago by mfranzke
  0

• Error: Input required and not supplied: token

  #31 opened 2 years ago by lastdoctor
  7

• Add an option to only allow incremental package versions to be published

  #43 opened 2 years ago by Tohaker
  1

• `Warning: Unexpected input(s) 'greater-version-only'` on action run

  #52 opened 2 years ago by WillsterJohnson
  0

• Token Authentication Failure on Publish to Custom Registry

  #33 opened 2 years ago by MitchCroft
  2

• Authenticate via Username / Password

  #21 opened 2 years ago by db5rg3ss
  2

• Any way to don't publish if not already published?

  #48 opened 2 years ago by SrBrahma
  3

• The registry parameter doesn't work

  #55 opened 2 years ago by honzabilek4
  2

• Invalid Version: 2023.01.17

  #70 opened 2 years ago by tpluscode
  2

• Publish function always reports publishing to NPM even when alternative registry is used

  #40 opened 3 years ago by rorysedgwick
  0

• Tarball content is "empty"

  #39 opened 3 years ago by josemarcilio
  1

• Not using `version` from `package.json`

  #38 opened 3 years ago by CWSites
  1

• Package successfully publishes to npmjs but also throws a 403

  #37 opened 4 years ago by Yrlish
  1

• Run in subfolder

  #34 opened 4 years ago by enyo
  1

• TypeError: Unable to parse package.json

  #32 opened 4 years ago by softmarshmallow
  1

• Release to GitHub Registry was failed.

  #26 opened 4 years ago by say8425
  2

• Version 1.4.1 throws error

  #29 opened 4 years ago by speelbarrow
  3

• Error: TypeError: Unable to determine the current version of @owner/repo on NPM.

  #24 opened 4 years ago by cpotter302
  3

• Getting 404 for first-time publish attempt

  #23 opened 4 years ago by IdanAdar
  2

• Publishing on PR

  #20 opened 4 years ago by shibdib
  1

• Publishing scoped packages

  #22 opened 4 years ago by IdanAdar
  1

• Create git tag

  #27 opened 4 years ago by rom1504
  1