fix(deps): update dependency @envelop/core to v5 #2127
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:
^3.0.6
->^5.0.3
Release Notes
n1ru4l/envelop (@envelop/core)
v5.0.3
Compare Source
Patch Changes
8d89758
Thanks @ardatan! - When the schema is the same, do not trigger
onSchemaChange
hookv5.0.2
Compare Source
Patch Changes
c3dd2c3
Thanks @ardatan! - Export
mapMaybePromise
andisPromise
v5.0.1
Compare Source
Patch Changes
dc1222f
Thanks @benjie! - feat: add
useValidationRule()
pluginv5.0.0
Compare Source
Major Changes
68e7a2a5
Thanks @EmrysMyrddin! - Breaking Change: Support of Node 16
is dropped.
#1939
f7ef03c0
Thanks @EmrysMyrddin! - The
addPlugin
function now insert theplugin in place in the plugin list, leading to a more predictable execution order.
Breaking Change: This change alter the execution order of plugins. This can break some plugins
that was relying on the fact the
addPlugin
allowed to push a plugin to the end of the pluginlist.
If it is the case, the best fix is to reorder the plugin list and ensure the plugin is in the
right position, after all its dependencies.
Patch Changes
[
68e7a2a5
]:v4.0.3
Patch Changes
dee6b8d2
Thanks @EmrysMyrddin! - The context is now referentialy stable.
It means the context passed to all hooks and to all resolver is guaranted to always be the same
object instance. This unique object instance will be mutated as needed to extend the context.
v4.0.2
Patch Changes
db20864a
Thanks @EmrysMyrddin! - Fixed plugin duplication when nesting
envelop extensions
v4.0.1
Compare Source
Patch Changes
[
834e1e39
]:v4.0.0
Compare Source
Major Changes
332f1f22
Thanks @ardatan! - Drop Node 14 and require Node 16 or higher
Patch Changes
a36925c7
Thanks @ardatan! - - Memoize parsed document string result and use
it wherever possible, and export
getDocumentString
function to allow users to use it as well.WeakMap
s withDocumentNode
wherever possible instead of using LRU Cache with strings. Itis more optimal if a parser caching is used
[
332f1f22
]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.