chore(deps): update all dependencies #915
Merged
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:
^7.23.6
->^7.23.7
^7.23.6
->^7.23.7
^7.23.6
->^7.23.7
^7.6.6
->^7.6.7
^7.6.6
->^7.6.7
^7.6.6
->^7.6.7
^7.6.6
->^7.6.7
^7.6.6
->^7.6.7
^7.6.6
->^7.6.7
^14.5.1
->^14.5.2
^20.10.5
->^20.10.6
^6.16.0
->^6.17.0
^6.16.0
->^6.17.0
0.3.4
->0.4.0
1.18.1
->1.19.0
^27.6.0
->^27.6.1
6.7.0
->7.0.1
4.17.3
->4.20.0
9.2.7
->9.5.3
7.4.3
->7.4.4
11.1.2
->13.0
5.2.3
->5.2.4
v1.12
->v1.13
^7.6.6
->^7.6.7
Release Notes
babel/babel (@babel/core)
v7.23.7
Compare Source
🐛 Bug Fix
babel-traverse
Program
(@liuxingbaoyu)babel-helpers
,babel-plugin-proposal-decorators
ctx.kind
is wrong (@liuxingbaoyu)babel-plugin-proposal-decorators
babel-core
unhandledRejection
events (@nicolo-ribaudo)🏠 Internal
babel-helper-create-class-features-plugin
babel-helper-create-class-features-plugin
,babel-plugin-proposal-decorators
storybookjs/storybook (@storybook/addon-essentials)
v7.6.7
Compare Source
storybookjs/storybook (@storybook/addon-interactions)
v7.6.7
Compare Source
storybookjs/storybook (@storybook/addon-links)
v7.6.7
Compare Source
testing-library/user-event (@testing-library/user-event)
v14.5.2
Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.17.0
Compare Source
Bug Fixes
patterns
orpaths
in options are empty (#8108) (675e987)Features
default
case on an already exhaustiveswitch
(#7539) (6a219bd)You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.17.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
splunk/addonfactory-splunk-conf-parser-lib (addonfactory-splunk-conf-parser-lib)
v0.4.0
Compare Source
Features
mtkennerly/dunamai (dunamai)
v1.19.0
Compare Source
--path
option to inspect a directory other than the current one.The
Version.from_*
methods now also take apath
argument.jest-community/eslint-plugin-jest (eslint-plugin-jest)
v27.6.1
Compare Source
Bug Fixes
meta
information with snapshot processor for ESLint v9 (#1484) (067e246)python/importlib_metadata (importlib-metadata)
v7.0.1
Compare Source
v7.0.0
Compare Source
v6.11.0
Compare Source
v6.10.0
Compare Source
v6.9.0
Compare Source
v6.8.0
Compare Source
python-jsonschema/jsonschema (jsonschema)
v4.20.0
Compare Source
=======
unevaluatedItems
(resp.unevaluatedProperties
) when behind a$dynamicRef
as specified by the 2020 and 2019 specifications.jsonschema.exceptions.ErrorTree.__setitem__
is now deprecated.More broadly, in general users of
jsonschema
should never be mutating objects owned by the library.v4.19.2
Compare Source
=======
additionalItems
keyword into JSON Schema draft 2020-12, where it was replaced byitems
.v4.19.1
Compare Source
=======
hostname
format.This is the behavior specified by the relevant RFC (1123).
IDN hostname behavior was already correct.
v4.19.0
Compare Source
=======
Validator
protocol directly from the package root is deprecated.Import it from
jsonschema.protocols.Validator
instead.Such resources are assumed to be 2020-12 schemas.
This more closely matches the pre-referencing library behavior.
v4.18.6
Compare Source
=======
jsonschema
specific user agent when automatically retrieving remote references (which is deprecated).v4.18.5
Compare Source
=======
v4.18.4
Compare Source
=======
v4.18.3
Compare Source
=======
applicable_validators
in extended validators.Specifically, validators extending early drafts where siblings of
$ref
were ignored will properly ignore siblings in the extended validator.v4.18.2
Compare Source
=======
jsonschema.RefResolver
and pointer resolution.v4.18.1
Compare Source
=======
jsonschema.RefResolver
based resolution when used in combination with a custom validation dialect (viajsonschema.validators.create
).v4.18.0
Compare Source
=======
This release majorly rehauls the way in which JSON Schema reference resolution is configured.
It does so in a way that should be backwards compatible, preserving old behavior whilst emitting deprecation warnings.
jsonschema.RefResolver
is now deprecated in favor of the newreferencing library <https://github.com/python-jsonschema/referencing/>
_.referencing
will begin in beta, but already is more compliant than the existing$ref
support.This change is a culmination of a meaningful chunk of work to make
$ref
resolution more flexible and more correct.Backwards compatibility should be preserved for existing code which uses
RefResolver
, though doing so is again now deprecated, and all such use cases should be doable using the new APIs.Please file issues on the
referencing
tracker if there is functionality missing from it, or here on thejsonschema
issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to usereferencing
.In particular, this referencing change includes a change concerning automatic retrieval of remote references (retrieving
http://foo/bar
automatically within a schema).This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings.
The
referencing
library itself will not automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default$ref
resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error).This should not be a "visible" change in the sense that
requires-python
has been updated, so users using 3.7 should still receivev4.17.3
when installing the library.unevaluatedItems
now properly does not consider items to be evaluated by anadditionalItems
schema ifitems
is missing from the schema, as the specification says in this case thatadditionalItems
must be completely ignored.date
format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal (#1076).unevaluatedProperties
(#1075).Deprecations
jsonschema.RefResolver
-- see above for details on the replacementjsonschema.RefResolutionError
-- see above for details on the replacementjsonschema.ErrorTree
-- instead import it viajsonschema.exceptions.ErrorTree
jsonschema.FormatError
-- instead import it viajsonschema.exceptions.FormatError
squidfunk/mkdocs-material (mkdocs-material)
v9.5.3
: mkdocs-material-9.5.3Compare Source
v9.5.2
: mkdocs-material-9.5.2Compare Source
slugify
settings in blog plugin configv9.5.1
: mkdocs-material-9.5.1Compare Source
v9.5.0
: mkdocs-material-9.5.0Compare Source
Merged Insiders features of 'Goat's Horn' funding goal
v9.4.14
: mkdocs-material-9.4.14Compare Source
v9.4.13
: mkdocs-material-9.4.13Compare Source
v9.4.12
: mkdocs-material-9.4.12Compare Source
v9.4.11
: mkdocs-material-9.4.11Compare Source
v9.4.10
: mkdocs-material-9.4.10Compare Source
v9.4.9
: mkdocs-material-9.4.9Compare Source
pt-BR
v9.4.8
: mkdocs-material-9.4.8Compare Source
v9.4.7
: mkdocs-material-9.4.7Compare Source
v9.4.6
: mkdocs-material-9.4.6Compare Source
v9.4.5
: mkdocs-material-9.4.5Compare Source
v9.4.4
: mkdocs-material-9.4.4Compare Source
v9.4.3
: mkdocs-material-9.4.3Compare Source
Updated templates (diff)
base.html
v9.4.2
: mkdocs-material-9.4.2Compare Source
nav
is defined and blog not includedUpdated templates (diff)
partials/nav-item.html
blog-post.html
v9.4.1
: mkdocs-material-9.4.1Compare Source
v9.4.0
: mkdocs-material-9.4.0Compare Source
materialx
v9.3.2
: mkdocs-material-9.3.2Compare Source
v9.3.1
: mkdocs-material-9.3.1Compare Source
v9.3.0
: mkdocs-material-9.3.0Compare Source
v9.2.8
: mkdocs-material-9.2.8Compare Source
pytest-dev/pytest (pytest)
v7.4.4
Compare Source
pytest-dev/pytest-rerunfailures (pytest-rerunfailures)
v13.0
Compare Source
Breaking changes
++++++++++++++++
Features
++++++++
Bug fixes
+++++++++
Fix crashitem names mismatch between client and server.
(
#​172 <https://github.com/pytest-dev/pytest-rerunfailures/issues/172>
_)Fix crash when setup fails with --rerun-except flag.
(
#​230 <https://github.com/pytest-dev/pytest-rerunfailures/issues/230>
_)v12.0
Compare Source
Breaking changes
++++++++++++++++
Features
++++++++
Add
only_rerun
andrerun_except
arguments to@pytest.mark.flaky
marker.Add support for pytest 7.3, 7.4.
Bug fixes
+++++++++
--only-rerun
pattern (if given) and none of the
--rerun-except
patterns. Previously,using both
--only-rerun
and--rerun-except
together could causefailures to be rerun even if they did not match any
--only-rerun
pattern, and when using multiple
--rerun-except
patterns, all failureswould be rerun unless they matched every pattern.
(
#​225 <https://github.com/pytest-dev/pytest-rerunfailures/issues/225>
_)splunk/addonfactory-test-matrix-action (splunk/addonfactory-test-matrix-action)
v1.13
Compare Source
Configuration
📅 Schedule: Branch creation - "every 2 weeks on Sunday" (UTC), 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.