Skip to content

issues Search Results · repo:JS-DevTools/npm-publish language:TypeScript

Filter by

66 results
 (65 ms)

66 results

inJS-DevTools/npm-publish (press backspace or delete to remove)

The README.md file s Changelog link is broken. I don t understand why, but it links to https://github.com/JS-DevTools/npm-publis/releases (note that it s npm-publis, not npm-publish).
  • forevermatt
  • Opened 
    on Jan 27
  • #221

Hi, I tried using this action to publish a basic package for the first time, but it didn t work; the action claims that it didn t find the package in the registry - which is fair, because it doesn t exist ...
  • Nawias
  • 2
  • Opened 
    on Nov 6, 2024
  • #220

Why this library throws the following error if I use any release different than {major}.{minor}.{patch}? Anything like {major}.{minor}.{patch}-snapshot or even {major}.{minor}.{patch}.something throws ...
more info needed
  • rrigoni
  • 3
  • Opened 
    on Jun 14, 2024
  • #202

Our method of shelling out to npm in Windows has been broken by a security fix in Node.js. Currently, all windows CI is failing due to this break. See https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2 ...
bug
  • mcous
  • Opened 
    on Jun 1, 2024
  • #198

Have you considered including more of the standard output of npm s dry run mode? I find that quite helpful sometimes, such as to see what all files would be included in the published package (so that I ...
  • forevermatt
  • 4
  • Opened 
    on Mar 20, 2024
  • #184

getting 404 error Error: NpmCallError: Call to npm publish exited with non-zero exit code 1 npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm ERR! code E404 ...
  • LoeiFy
  • 1
  • Opened 
    on Mar 11, 2024
  • #182

Hello! Not sure how I arrived at this particular error. I believe these are the salient parts of my workflow file: - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v3 ...
  • michaelnlindsay
  • 6
  • Opened 
    on Oct 24, 2023
  • #160

Hi, I ve got an issue. Even if a npm package altready exists with the current version, the gh action wants to publish it again: npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@xxx%2fxxx ...
bug
  • scraly
  • 2
  • Opened 
    on Sep 12, 2023
  • #139

Setup: - name: Publish New ESLint Release on npm uses: JS-DevTools/npm-publish@v2 with: token: ${{ secrets.NPM_PUBLISH_TOKEN }} strategy: upgrade - if: ...
  • johnnyshankman
  • 1
  • Opened 
    on Aug 9, 2023
  • #128

Hi, our NPM publish failed after your (much-appreciated) change to upgrade us to npm-publish@v2: https://github.com/matrix-org/matrix-react-sdk/actions/runs/5520127165/jobs/10066320474 but the error ...
bug
  • andybalaam
  • 6
  • Opened 
    on Jul 11, 2023
  • #119
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub