meteor-react-native
meteor-react-native copied to clipboard
build(deps): bump the npm_and_yarn group with 3 updates
Bumps the npm_and_yarn group with 3 updates: braces, lint-staged and elliptic.
Updates braces from 3.0.2 to 3.0.3
Commits
74b2db23.0.388f1429update eslint. lint, fix unit tests.415d660Snyk js braces 6838727 (#40)190510ffix tests, skip 1 test in test/braces.expand716eb9freadme bumpa5851e5Merge pull request #37 from coderaiser/fix/vulnerability2092bd1feature: braces: add maxSymbols (https://github.com/micromatch/braces/issues/...9f5b4cffix: vulnerability (https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727)98414f9remove funding file665ab5dupdate keepEscaping doc (#27)- Additional commits viewable in compare view
Updates lint-staged from 7.3.0 to 15.2.10
Release notes
Sourced from lint-staged's releases.
v15.2.10
Patch Changes
v15.2.9
Patch Changes
- #1463
b69ce2dThanks@iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected.v15.2.8
Patch Changes
f0480f0Thanks@iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
v15.2.7
Patch Changes
- #1440
a51be80Thanks@iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version drops the--path-format=absoluteoption to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggitto the latest version.v15.2.6
Patch Changes
- #1433
119adb2Thanks@iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.v15.2.5
Patch Changes
#1424
31a1f95Thanks@iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0Thanks@iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15Thanks@iiroj! - Upgrade [email protected]v15.2.4
Patch Changes
v15.2.3
Patch Changes
v15.2.2
Patch Changes
... (truncated)
Changelog
Sourced from lint-staged's changelog.
15.2.10
Patch Changes
15.2.9
Patch Changes
- #1463
b69ce2dThanks@iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected.15.2.8
Patch Changes
f0480f0Thanks@iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
15.2.7
Patch Changes
- #1440
a51be80Thanks@iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version drops the--path-format=absoluteoption to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggitto the latest version.15.2.6
Patch Changes
- #1433
119adb2Thanks@iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.15.2.5
Patch Changes
#1424
31a1f95Thanks@iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0Thanks@iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15Thanks@iiroj! - Upgrade [email protected]15.2.4
Patch Changes
15.2.3
... (truncated)
Commits
163112fchore(changeset): release829575cMerge pull request #1471 from lint-staged/updates893ca84refactor: remove unused parameter defaulta661f46build(deps): migrate to ESLint 9e3f283bbuild(deps): update minor dependencies35483b9docs: add some more concrete command examples to the README0ce5e14chore(changeset): release (#1465)b69ce2dfix: set max event listeners to the number of tasks (#1463)52f6eefchore(changeset): release (#1462)8d8fe23build: update repository url in package.json- Additional commits viewable in compare view
Updates elliptic from 6.5.4 to 6.5.7
Commits
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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.