Bump lockfile-lint from 4.2.2 to 4.3.3#89
Bump lockfile-lint from 4.2.2 to 4.3.3#89dependabot-preview[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [lockfile-lint](https://github.com/lirantal/lockfile-lint) from 4.2.2 to 4.3.3. - [Release notes](https://github.com/lirantal/lockfile-lint/releases) - [Commits](https://github.com/lirantal/lockfile-lint/compare/lockfile-lint@4.2.2...lockfile-lint@4.3.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
|
The test failure here looks like a false positive. Looks like it's treating |
|
The other changelog files disable that rule at the top, but the v14 one doesn't |
|
Superseded by #90. |
Still don't understand why |
|
Not sure, the only other diff I can see upstream, is that it's still running remark-lint v6 instead of v7, but I don't know if that would really cause an issue |
Updating remark-lint didn't replicate it, but updating all the deps did. Thanks! |
Add a comment to disable a rule in the 14.x changelog that will be needed once we update remark lint dependencies. This comment appears in the other changelogs. Refs: nodejs/remark-preset-lint-node#89 (comment) PR-URL: nodejs#33412 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Add a comment to disable a rule in the 14.x changelog that will be needed once we update remark lint dependencies. This comment appears in the other changelogs. Refs: nodejs/remark-preset-lint-node#89 (comment) PR-URL: #33412 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Bumps lockfile-lint from 4.2.2 to 4.3.3.
Commits
a9bf211chore(release): publish7d239cafix: bump package ver that skipped releases4e41761chore(release): publish828868cfix(readme): update example 3 remove invalid argument (#90)a939b5fchore(release): publishd0002e7fix(hostvalidator): support full urls for host (#88)3ff6eb8feat: add validation success console message (#87)c311c44test: fix hosts validator tests (#85)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard: