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

build(deps-dev): bump lockfile-lint from 4.12.0 to 4.12.1 #1797

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2023

Bumps lockfile-lint from 4.12.0 to 4.12.1.

Release notes

Sourced from lockfile-lint's releases.

lockfile-lint@4.12.1

Patch Changes

  • 745aa65 Thanks @​lirantal! - fix: --version command-line was throwing an error related to glob matching
Changelog

Sourced from lockfile-lint's changelog.

4.12.1

Patch Changes

  • 745aa65 Thanks @​lirantal! - fix: --version command-line was throwing an error related to glob matching
Commits
  • 7958b39 chore: new release (#185)
  • 7e1d41d test: add test cases for future regressions
  • ed61024 docs: update -p command-line instructions relating to glob matching
  • a45ff60 fix: glob always expecting path to be provided
  • See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 [lockfile-lint](https://github.com/lirantal/lockfile-lint/tree/HEAD/packages/lockfile-lint) from 4.12.0 to 4.12.1.
- [Release notes](https://github.com/lirantal/lockfile-lint/releases)
- [Changelog](https://github.com/lirantal/lockfile-lint/blob/main/packages/lockfile-lint/CHANGELOG.md)
- [Commits](https://github.com/lirantal/lockfile-lint/commits/lockfile-lint@4.12.1/packages/lockfile-lint)

---
updated-dependencies:
- dependency-name: lockfile-lint
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/lockfile-lint-4.12.1 branch from b9cc255 to 7b7d35f Compare September 12, 2023 14:36
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 13, 2023

Looks like lockfile-lint is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Sep 13, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/lockfile-lint-4.12.1 branch September 13, 2023 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants