chore(deps): update external major (major) #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
This PR will trigger no release when merged. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #33 +/- ##
=======================================
Coverage 96.12% 96.12%
=======================================
Files 12 12
Lines 1366 1366
=======================================
Hits 1313 1313
Misses 53 53 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
23f1f6b
to
650bc48
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
650bc48
to
9faad3a
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
9faad3a
to
faba371
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
a929116
to
6c3bc82
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
2b61ebc
to
2539bc1
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
2539bc1
to
6ce2324
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
5 times, most recently
from
da5d8c8
to
2046929
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
4 times, most recently
from
a800c1b
to
aab2eff
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
03b753e
to
2364b3d
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
4 times, most recently
from
c41ba36
to
adb9c12
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
58ba21f
to
555ad3f
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
6a91fa5
to
81fd70e
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
5 times, most recently
from
869ab70
to
fefe907
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
3 times, most recently
from
260c327
to
e5a1237
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
df2ccfa
to
54ee227
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
35eb205
to
0eeead7
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
0eeead7
to
24d85fc
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
3 times, most recently
from
63f8ecb
to
4787195
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
4787195
to
a36aa94
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
a36aa94
to
44c3150
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
3 times, most recently
from
db5386e
to
bea02f4
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
2 times, most recently
from
62665c7
to
bf16471
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
bf16471
to
f745ef6
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
4 times, most recently
from
325170f
to
1cc14ea
Compare
renovate
bot
force-pushed
the
renovate-major-external-major
branch
from
1cc14ea
to
961c4eb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.0.6->12.0.1v3->v4v3->v47.14.0->10.1.23.3.0->4.1.0^5.0.4->^6.0.0v2->v38.0.3->9.0.1113.3.0->15.2.7^3.0.0->^4.0.021.1.2->24.0.0^15.0.4->^18.0.0Release Notes
semantic-release/npm (@semantic-release/npm)
v12.0.1Compare Source
Bug Fixes
v12.0.0Compare Source
Features
exportsto point at ./index.js (9e193c2)BREAKING CHANGES
exportshas been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.0.3Compare Source
Bug Fixes
even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully
v11.0.2Compare Source
Bug Fixes
v11.0.1Compare Source
Bug Fixes
v11.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
actions/checkout (actions/checkout)
v4Compare Source
actions/setup-node (actions/setup-node)
v4Compare Source
bcoe/c8 (c8)
v10.1.2Compare Source
Bug Fixes
v10.1.1Compare Source
Bug Fixes
v10.1.0Compare Source
Features
v10.0.0Compare Source
⚠ BREAKING CHANGES
Bug Fixes
v9.1.0Compare Source
Features
Bug Fixes
v9.0.0Compare Source
⚠ BREAKING CHANGES
Features
v8.0.1Compare Source
Bug Fixes
v8.0.0Compare Source
⚠ BREAKING CHANGES
Miscellaneous Chores
jonbern/fetch-retry (fetch-retry)
v6.0.0: Permissive wrapping, fix global pollution and export typesCompare Source
Adds permissive wrapping of the
fetchfunction while retaining the original typing of the wrapped library. This enables us to handle that there are slight variations betweenfetchimplementations in node.This change also removes the need for the triple-slash directive which polluted the global namespace with DOM typings. The new version also exports all the types defined in the library for good measure.
Many thanks to @alecmev for providing an excellent PR which made these changes possible.
github/codeql-action (github/codeql-action)
v3Compare Source
typicode/husky (husky)
v9.0.11Compare Source
v9.0.10Compare Source
v9.0.9Compare Source
v9.0.8Compare Source
v9.0.7Compare Source
~/.huskyrccorrectly (compatibility with v8)v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
v9.0.2Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.0.1...v9.0.2
v9.0.1Compare Source
Kicking off the year with an exciting update!
TLDR;
Improved user experience and a (even) smaller package size while packing in more features!
👋 By the Way
I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂
Introducing
husky initAdding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.
v8
v9
Adding a New Hook
Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic
echocommand.v8
v9
Further Size Reduction
v8was already the most compact Git hooks manager at approximately6kB.v9takes this a step further, reducing the size to just3kB, likely making it the smallest devDependency in your toolkit.To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for
v9. Stay tuned 🙌Other Changes
--provenancefor safer publishing.$XDG_CONFIG_HOMEsupport. Move~/.huskyrcto~/.config/husky/init.shfor centralized configuration.husky install. Usehuskyorhusky some/dirfor the same functionality (deprecation notice to be added)..gitis missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1withHUSKY=2for debugging.ESMfor module usage.How to Migrate
v9is backward compatible withv8, allowing you to freely upgrade and migrate your hooks later.package.json{ "scripts": { - "prepare": "husky install" + "prepare": "husky" } }.husky/pre-commitokonet/lint-staged (lint-staged)
v15.2.7Compare Source
Patch Changes
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.6Compare Source
Patch Changes
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.5Compare Source
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 micromatch@4.0.7v15.2.4Compare Source
Patch Changes
4f4537aThanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2Compare Source
Patch Changes
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.1Compare Source
Patch Changes
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.0Compare Source
Minor Changes
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 lilconfig@3.0.0#1368
7c55ca9Thanks @iiroj! - Update most dependencies#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.0Compare Source
Minor Changes
0423311Thanks @danielbayley! - Add support for loading configuration frompackage.yamlandpackage.ymlfiles, supported bypnpm.Patch Changes
105d901Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2Compare Source
Patch Changes
8e82364Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.v15.0.1Compare Source
Patch Changes
d2e6f8bThanks @louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.v15.0.0Compare Source
Major Changes
#1322
66b93aaThanks @iiroj! - Require at least Node.js 18.12.0This release drops support for Node.js 16, which is EOL after 2023-09-11.
Please upgrade your Node.js to the latest version.
Additionally, all dependencies have been updated to their latest versions.
v14.0.1Compare Source
Bug Fixes
v14.0.0Compare Source
Features
BREAKING CHANGES
16.14.0.broofa/mime (mime)
v4.0.3Compare Source
v4.0.2Compare Source
v4.0.1Compare Source
v4.0.0Compare Source
semantic-release/semantic-release (semantic-release)
v24.0.0Compare Source
Bug Fixes
BREAKING CHANGES
conventional-changelog packages. if you are installing any of these packages in addition to
semantic-release, be sure to update them as well
versions of conventional-changelog packages. if you are installing any of these packages in addition
to semantic-release, be sure to update them as well
v23.1.1Compare Source
v23.1.0Compare Source
v23.0.8Compare Source
Bug Fixes
v23.0.7Compare Source
v23.0.6Compare Source
Bug Fixes
v23.0.5Compare Source
v23.0.4Compare Source
v23.0.3Compare Source
v23.0.2Compare Source
Bug Fixes
v23.0.1Compare Source
Bug Fixes
v23.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://github.com/semantic-release/semantic-release/discussions/3088
release.config.jsas the name of your config file, it needs to be moved to a.config/directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12Compare Source
Bug Fixes
v22.0.11Compare Source
Bug Fixes
v22.0.10Compare Source
Bug Fixes
v22.0.9Compare Source
Bug Fixes
v22.0.8Compare Source
Bug Fixes
v22.0.7Compare Source
Bug Fixes
Features
v22.0.6Compare Source
Bug Fixes
v22.0.5Compare Source
Bug Fixes
v22.0.4Compare Source
Bug Fixes
v22.0.3Compare Source
Bug Fixes
exportsdefinition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2Compare Source
Bug Fixes
v22.0.1Compare Source
Bug Fixes
release-notes-generatorandcommit-analyzerplugins to stable versions (041e4f7), closes #2934v22.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
sinonjs/sinon (sinon)
v18.0.0Compare Source
This is what 17.0.2 should have been, as that contained two breaking changes. After updating
Nise we are down to one breaking change, which only affects sinon-test (which has been updated),
so most people are not affected. The legacyRoutes flag that is currently enabled in Nise by default
will at some later version be disabled. We will then issue a little migration note.
01d45312Use Nise 6 with legacyRoutes flag enabled (Carl-Erik Kopseng)
c618edc5fix #2594: remove needless sandbox creation (Carl-Erik Kopseng)
Released by Carl-Erik Kopseng on 2024-05-15.
v17.0.2Compare Source
f6dca0baupgrade packages (#2595) (Carl-Erik Kopseng)
5025d001Avoid return and callArg* clearing each other's state (#2593) (Carl-Erik Kopseng)
ed068a88Bump ip from 1.1.8 to 1.1.9 (#2587) (dependabot[bot])
ec4d592efix #2589: avoid invoking getter as side-effect (#2592) (Carl-Erik Kopseng)
9972e1e3Fix typo in mocks documentation (#2591) (Eduardo de la Cruz Palacios)
52e6e4c5chore: prefer cache option of setup-node (Morgan Roderick)
08da1235Bump actions/cache from 3 to 4 (dependabot[bot])
404ef47eBump nokogiri from 1.14.3 to 1.16.2 (dependabot[bot])
fd79612cUpdate Bug_report.md (Carl-Erik Kopseng)
1fbc812aRe-add about (Carl-Erik Kopseng)
fc8f6c3eFix formatting :clown: (Carl-Erik Kopseng)
c57e38aeRemove old template (Carl-Erik Kopseng)
754bf7a9Update Bug_report.md (Carl-Erik Kopseng)
87eed9d2Fix some typos at code comments (#2581) (EliyahuMachluf)
cbae6997Link to createStubInstance util.md docs in stubs.md (#2577) (Daniel Kaplan)
adcf936dFix Mocha watch task by delegating to Node (#2573) (Carl-Erik Kopseng)
30ad2372prettier:write (Carl-Erik Kopseng)
45c4d6b9Remove outdated info from README (#2571) (Carl-Erik Kopseng)
6c9f5c2aAdd a notice that the Fake Timers API doc is incomplete (#2570) (Carl-Erik Kopseng)
93db3ef3](httpConfiguration
📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.