Bump neostandard from 0.12.2 to 0.13.0#223
Conversation
Bumps [neostandard](https://github.com/neostandard/neostandard) from 0.12.2 to 0.13.0. - [Release notes](https://github.com/neostandard/neostandard/releases) - [Changelog](https://github.com/neostandard/neostandard/blob/main/CHANGELOG.md) - [Commits](neostandard/neostandard@v0.12.2...v0.13.0) --- updated-dependencies: - dependency-name: neostandard dependency-version: 0.13.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
@bcomnes Huh! Should we do something to catch this sooner or is this a false positive? |
|
I think its just a potential typosquat, but looking at it, it just seems like it was a less popular implementation of another one. Though I'm not sure why this diff is surfacing this. |
Bumps neostandard from 0.12.2 to 0.13.0.
Release notes
Sourced from neostandard's releases.
Changelog
Sourced from neostandard's changelog.
Commits
cc16b7echore(main): release 0.13.0 (#337)d3af897chore(dependents): update canary npm data (#346)d95b6e3fix(deps): update dependency find-up to v8 (#324)fe4ba92feat(deps): update dependency typescript-eslint to ^8.56.0 (#357)bb772acchore(deps): update all non-major dev dependencies (#352)caed7a7chore(deps): update dependency npm-run-all2 to v8 (#294)33c7dd8chore(deps): update dependency installed-check to v10 (#359)94ab3cefix(deps): update dependency globals to ^17.3.0 (#351)b873608fix(deps): update dependency peowly to ^1.3.3 (#356)ba575f3feat!: Require Node.js^20.19.0 || ^22.13.0 || >=24(#339)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for neostandard since your current version.
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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)