fix(deps): update external major (major) #10
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:
1.34.5
->2.0.2
7.0.0
->8.0.2
16.6.1
->17.2.1
15.5.2
->16.1.2
20.0.0
->21.0.0
Release Notes
Redocly/redocly-cli (@redocly/cli)
v2.0.2
Compare Source
Patch Changes
executionTimeout
parameter optional in therun
function exported fromrespect-core
.v2.0.1
Compare Source
Patch Changes
no-required-schema-properties-undefined
rule incorrectly resolved nested$ref
s relative to the file in which they were defined.v2.0.0
Compare Source
Major Changes
spec
rule. Usestruct
instead.apiDefinitions
option in the Redocly config. Useapis
instead.Removed the
labels
field within theapis
section, which was associated with the legacy Redocly API Registry product.redocly.yaml
.features.openapi
andfeatures.mockServer
configuration options. Useopenapi
andmockServer
directly instead.lint
andstyleguide
options in the Redocly config.Use
rules
,decorators
and other related options on the root level instead.disallowAdditionalProperties
option support in rules. UseallowAdditionalProperties
instead.theme
property of Redocly config.All the properties of
theme
are now available in the config root.path-excludes-patterns
andinfo-license-url
rules.undefined
assertion. Usedefined
instead.Reunite provides improved API management capabilities and better integration with Redocly's tooling ecosystem.
Migrated the
login
andpush
commands to work exclusively with Reunite.Removed the
preview-docs
command as part of platform modernization.Use the
preview
command instead.referenceDocs
option, which was related to the legacy Reference docs product.assert/
prefix in configurable rules. Userule/
prefix instead.Update to Node.js version 20.19.0+, 22.12.0+, or 23+.
Minor Changes
Added
x-security
extension for Respect that enables secure handling of authentication in Arazzo workflows.Use this extension to:
Added environment variable support for CLI arguments using Yargs
.env()
method to parse environment variables with matching prefixes.Added validation for JSON Schema format.
Extracted
nullable
validation from thestruct
rule into a newnullable-type-sibling
rule for OpenAPI 3.0. This allows users to disablenullable
validation separately from other structural checks.Configured the
spec
ruleset for OpenAPI, AsyncAPI, Arazzo, and Overlay specifications.This ruleset is designed to strictly follow the specifications.
Added the
no-duplicated-tag-names
rule to check for duplications in thetags
field in API descriptions.Enabled
no-required-schema-properties-undefined
,no-schema-type-mismatch
, andno-enum-type-mismatch
rules for AsyncAPI and Arazzo specifications.Adjusted the rules' severities in the
recommended
andminimal
rulesets. Refer to the following table:off
->warn
off
->warn
error
warn
warn
->error
off
->warn
Implemented automatic masking of sensitive fields (such as tokens and passwords) in response bodies to enhance security and prevent accidental exposure of secrets in logs and outputs.
Added new CLI options for the
respect
command to improve test execution control.Patch Changes
extends
section.no-undefined-server-variable
crash when encounteringnull
values in the server list.@redocly/respect-core
to eliminate Node.js-specific dependencies, improving cross-platform compatibility.--config
from a different folder than the current working directory.[email protected]
injected an unintended message into the output.residency
from the Redocly configuration file.kpdecker/jsdiff (diff)
v8.0.2
Compare Source
diffSentences
with old Safari versions. This was broken in 8.0.0 by the introduction of a regex with a lookbehind assertion; these weren't supported in Safari prior to version 16.4.sideEffects: false
.v8.0.1
Compare Source
diffJson
which were broken by 8.0.0. The new bundled types in 8.0.0 only alloweddiffJson
to be passed string arguments, but it should've been possible to pass either strings or objects (and now is). Thanks to Josh Kelley for the fix.v8.0.0
Compare Source
diffSentences
:["foo.", " ", "bar."]
but "foo. bar" tokenized to["foo.", " bar"]
- i.e. whether the space between sentences was treated as a separate token depended upon whether the final sentence had trailing punctuation or not. This was arbitrary and surprising; it is no longer the case.)diffWords
taking O(n^2) time in pathological cases.push()
using.apply
or the spread operator and hitting the JS-implementation-specific limit on the maximum number of arguments to a function, as shown at https://stackoverflow.com/a/56809779/1709587; thus the exact threshold to hit the error will depend on the environment in which you were running JsDiff.)merge
function. Previously JsDiff included an undocumented function calledmerge
that was meant to, in some sense, merge patches. It had at least a couple of serious bugs that could lead to it returning unambiguously wrong results, and it was difficult to simply "fix" because it was unclear precisely what it was meant to do. For now, the fix is to remove it entirely.the
diff
package on npm now includes its own TypeScript type definitions. Users who previously used the@types/diff
npm package from DefinitelyTyped should remove that dependency when upgrading JsDiff to v8.Note that the transition from the DefinitelyTyped types to JsDiff's own type definitions includes multiple fixes and also removes many exported types previously used for
options
arguments to diffing and patch-generation functions. (There are now different exported options types for abortable calls - ones with atimeout
ormaxEditLength
that may give a result ofundefined
- and non-abortable calls.) See the TypeScript section of the README for some usage tips.The
Diff
object is now a class. Custom extensions ofDiff
, as described in the "Defining custom diffing behaviors" section of the README, can therefore now be done by writing aclass CustomDiff extends Diff
and overriding methods, instead of the old way based on prototype inheritance. (I think code that did things the old way should still work, though!)diff/lib/index.es6.js
anddiff/lib/index.mjs
no longer exist, and the ESM version of the library is no longer bundled into a single file.The
ignoreWhitespace
option fordiffWords
is no longer included in the type declarations. The effect of passingignoreWhitespace: true
has always been to makediffWords
just calldiffWordsWithSpace
instead, which was confusing, because that behaviour doesn't seem properly described as "ignoring" whitespace at all. The property remains available to non-TypeScript applications for the sake of backwards compatibility, but TypeScript applications will now see a type error if they try to passignoreWhitespace: true
todiffWords
and should change their code to calldiffWordsWithSpace
instead.JsDiff no longer purports to support ES3 environments. (I'm pretty sure it never truly did, despite claiming to in its README, since even the 1.0.0 release used
Array.map
which was added in ES5.)diffJson
'sstringifyReplacer
option behaves more likeJSON.stringify
'sreplacer
argument now. In particular:key
passed to the replacer when the top-level object is passed in asvalue
is now""
(previously, wasundefined
), and thekey
passed with an array element is the array index as a string, like"0"
or"1"
(previously was whatever the key for the entire array was). Both the new behaviours match that ofJSON.stringify
.undefined
when called in async mode (i.e. with a callback). Previously, there was an odd quirk where they would returntrue
if the strings being diffed were equal andundefined
otherwise.motdotla/dotenv (dotenv)
v17.2.1
Compare Source
Changed
v17.2.0
Compare Source
Added
DOTENV_CONFIG_QUIET=true
in your environment or.env
file to quiet the runtime log (#889)DOTENV_CONFIG_
environment variables take precedence over any code set options like({quiet: false})
v17.1.0
Compare Source
Added
v17.0.1
Compare Source
Changed
v17.0.0
Compare Source
Changed
quiet
to false - informational (file and keys count) runtime log message shows by default (#875)lint-staged/lint-staged (lint-staged)
v16.1.2
Compare Source
Patch Changes
#1570
a7c0c88
Thanks @ItsNickBarry! - When using--diff-filter
with theD
option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit add
likefatal: pathspec 'deleted-file' did not match any files
.38f942e
Thanks @iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFiles
to console output.v16.1.1
Compare Source
Patch Changes
#1565
3686977
Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using--no-stash
.#1571
02299a9
Thanks @iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.#1563
bc61c74
Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stash
option. This happened because--no-stash
implied--no-hide-partially-staged
, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.The previous (incorrect) behavior can still be achieved by using both options
--no-stash --no-hide-partially-staged
at the same time.v16.1.0
Compare Source
Minor Changes
#1536
e729daa
Thanks @iiroj! - A new flag--no-revert
has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.#1550
b27fa3f
Thanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.Patch Changes
c37dc38
Thanks @iiroj! - The minimum required Node.js version is lowered to20.17
following [email protected].v16.0.0
Compare Source
Major Changes
#1546
158d15c
Thanks @iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them withnode
, especially when using Windows:#1546
158d15c
Thanks @iiroj! - The--shell
flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via"$@​"
:sinonjs/sinon (sinon)
v21.0.0
Compare Source
fd10f13f
chore!: remove assert.failException property (#2659) (Morgan Roderick)
Released by Morgan Roderick on 2025-06-13.
Configuration
📅 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 was generated by Mend Renovate. View the repository job log.