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 validate-npm-package-name from 3.0.0 to 5.0.0 #258

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 18, 2022

Bumps validate-npm-package-name from 3.0.0 to 5.0.0.

Release notes

Sourced from validate-npm-package-name's releases.

v5.0.0

5.0.0 (2022-10-10)

⚠️ BREAKING CHANGES

  • validate-npm-package-name is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

Features

v4.0.0

4.0.0 (2022-03-29)

⚠ BREAKING CHANGES

  • scopedPackagePattern is no longer exported from this module.
  • This drops support for node 10 and non-LTS versions of node 12 and node 14

Features

Bug Fixes

  • remove validate.scopedPackagePattern (#42) (1943cc6)

Documentation

  • Move invalid example to the right section (#18) (9ee8d54)
  • update misleading naming rule (#27) (3c65535)

Dependencies

Changelog

Sourced from validate-npm-package-name's changelog.

5.0.0 (2022-10-10)

⚠️ BREAKING CHANGES

  • validate-npm-package-name is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

Features

4.0.0 (2022-03-29)

⚠ BREAKING CHANGES

  • scopedPackagePattern is no longer exported from this module.
  • This drops support for node 10 and non-LTS versions of node 12 and node 14

Features

Bug Fixes

  • remove validate.scopedPackagePattern (#42) (1943cc6)

Documentation

  • Move invalid example to the right section (#18) (9ee8d54)
  • update misleading naming rule (#27) (3c65535)

Dependencies

Commits
  • 5e4965a chore: release 5.0.0 (#52)
  • 2cb325d chore: postinstall for dependabot template-oss PR
  • 215841d chore: bump @​npmcli/template-oss from 4.4.4 to 4.5.1
  • 120c612 chore: postinstall for dependabot template-oss PR
  • 92bfcbe chore: bump @​npmcli/template-oss from 4.3.2 to 4.4.4
  • f0983ef feat!: postinstall for dependabot template-oss PR
  • 5ba262a chore: bump @​npmcli/template-oss from 3.5.0 to 4.3.2
  • 158c74c chore: bump @​npmcli/template-oss from 3.4.2 to 3.4.3 (#47)
  • 949ef34 chore: postinstall for dependabot template-oss PR
  • a3bb84d chore: bump @​npmcli/template-oss from 3.4.1 to 3.4.2
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by lukekarrys, a new releaser for validate-npm-package-name since your current version.


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 [validate-npm-package-name](https://github.com/npm/validate-npm-package-name) from 3.0.0 to 5.0.0.
- [Release notes](https://github.com/npm/validate-npm-package-name/releases)
- [Changelog](https://github.com/npm/validate-npm-package-name/blob/main/CHANGELOG.md)
- [Commits](npm/validate-npm-package-name@v3.0.0...v5.0.0)

---
updated-dependencies:
- dependency-name: validate-npm-package-name
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 18, 2022
@codecov
Copy link

codecov bot commented Oct 18, 2022

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (8e9f547) compared to base (5f29ce0).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##           develop      #258   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           86        86           
  Branches        17        17           
=========================================
  Hits            86        86           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Development

Successfully merging this pull request may close these issues.

2 participants