Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump JS-DevTools/npm-publish from 1.4.3 to 2.1.0 #137

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 3, 2023

Bumps JS-DevTools/npm-publish from 1.4.3 to 2.1.0.

Release notes

Sourced from JS-DevTools/npm-publish's releases.

v2.1.0

Features

  • Add explicit support for --provenance (#92), closes #88

Bug Fixes

  • Handle missing latest tag during version check (#90), closes #89

v2.0.0

Welcome to v2 of JS-DevTools/npm-publish! We've been doing some spring cleaning to fix all our (known) bugs and knock out some longstanding feature requests. This release has some breaking changes, so please read carefully!

BREAKING CHANGES

  • The type output is now an empty string instead of none when no release occurs

    - - if: ${{ steps.publish.outputs.type != 'none' }}
    + - if: ${{ steps.publish.outputs.type }}
        run:  echo "Version changed!"
  • The check-version and greater-version-only options have been removed and replaced with strategy.

    • Use strategy: all (default) to publish all versions that do not yet exist in the registry.
        with:
          token: ${{ secrets.NPM_TOKEN }}
      -   check-version: true
      -   greater-version-only: false
      +   strategy: all
    • Use strategy: upgrade to only publish versions that upgrade the selected tag.
        with:
          token: ${{ secrets.NPM_TOKEN }}
      -   check-version: true
      -   greater-version-only: true
      +   strategy: upgrade
    • check-version: false has been removed. You don't need this action if you're not checking already published versions; use npm directly, instead.
  • The library and CLI now require Node v16 or later. They may technically work in earlier versions, but they're not tested in CI and you will have to tell your package manager to ignore the engines requirement.

  • The library and CLI no longer read the user's ~/.npmrc file, so the token option is now required.

Features

  • tag, access, and registry now fall back to publishConfig in package.json, if specified. (#36)
  • The package argument may now be a directory, and is passed to npm publish as its package_spec argument. (#59)
  • The package argument may also be a pre-packed .tgz archive (#81)

Bug fixes

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [JS-DevTools/npm-publish](https://github.com/JS-DevTools/npm-publish) from 1.4.3 to 2.1.0.
- [Release notes](https://github.com/JS-DevTools/npm-publish/releases)
- [Changelog](https://github.com/JS-DevTools/npm-publish/blob/main/CHANGELOG.md)
- [Commits](JS-DevTools/npm-publish@0f451a9...541aa6b)

---
updated-dependencies:
- dependency-name: JS-DevTools/npm-publish
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner May 3, 2023 09:04
@dependabot dependabot bot added the dependencies Auto-pinning label May 3, 2023
@dbanck
Copy link
Member

dbanck commented May 3, 2023

Resolved by #136

@dbanck dbanck closed this May 3, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github May 3, 2023

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/github_actions/JS-DevTools/npm-publish-2.1.0 branch May 3, 2023 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Auto-pinning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant