meteor-react-native
meteor-react-native copied to clipboard
build(deps): bump the npm_and_yarn group across 1 directory with 2 updates
Bumps the npm_and_yarn group with 2 updates in the / directory: braces and lint-staged.
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.6
Release notes
Sourced from lint-staged's releases.
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
- #1391
fdcdad4Thanks@iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.v15.2.1
Patch Changes
- #1387
e4023f6Thanks@iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdinof the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdinis ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.v15.2.0
Minor Changes
- #1371
f3378beThanks@iiroj! - Using the--no-stashflag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag--no-hide-partially-stagedthat is automatically enabled when--no-stashis used.Patch Changes
#1362
17bc480Thanks@antonk52! - update [email protected]#1368
777d4e9Thanks@iiroj! - To improve performance, only uselilconfigwhen searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0ddThanks@iiroj! - When determining git directory, usefs.realpath()only for symlinks. It looks likefs.realpath()changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0
... (truncated)
Changelog
Sourced from lint-staged's changelog.
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
Patch Changes
15.2.2
Patch Changes
- #1391
fdcdad4Thanks@iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.15.2.1
Patch Changes
- #1387
e4023f6Thanks@iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdinof the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdinis ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.15.2.0
Minor Changes
- #1371
f3378beThanks@iiroj! - Using the--no-stashflag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag--no-hide-partially-stagedthat is automatically enabled when--no-stashis used.Patch Changes
- #1362
17bc480Thanks@antonk52! - update [email protected]
... (truncated)
Commits
a91d942chore(changeset): release119adb2fix: use native git command to get .git directorye0386dcfix: use native git command to get top-level directory for repo6593870ci: test Node.js versions against current instead of latest dependency6c226c5ci: add workflow for testing required Node.js semver rangef7e4106chore(changeset): releasefc75303build(release): lower next version bump from minor to patch91abea0fix: improve error logging when failing to parse config file (#1423)31a1f95build(deps): allow approximately equivalent versions of direct dependenciesee43f15build(deps): upgrade [email protected]- Additional commits viewable in compare view
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.