-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency js-yaml to v4 #3238
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/js-yaml-4.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 10:45
a68ae83
to
49fe730
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 12:15
49fe730
to
b1e919b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 13:40
b1e919b
to
581e311
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 14:14
581e311
to
f7958a6
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 15:01
f7958a6
to
5d04eac
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 15:10
5d04eac
to
a53ea06
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 12, 2024 19:06
a53ea06
to
d4a5763
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 13, 2024 05:57
d4a5763
to
8717dab
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 13, 2024 09:22
8717dab
to
6ed7e7b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 13, 2024 16:27
6ed7e7b
to
9d925be
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 09:10
9d925be
to
1cffc13
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 09:49
1cffc13
to
b633f28
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 13:33
b633f28
to
a882dce
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 13:51
a882dce
to
84762a9
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 14:23
84762a9
to
b3898d9
Compare
Its breaking |
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 14, 2024 17:08
b3898d9
to
383890e
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 16, 2024 10:23
383890e
to
0c3c92f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 16, 2024 13:12
0c3c92f
to
d02b84b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 16, 2024 16:05
d02b84b
to
73d765c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 16, 2024 18:50
73d765c
to
b497bfd
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 19, 2024 09:06
b497bfd
to
b815819
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 20, 2024 09:07
b815819
to
6085872
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 20, 2024 10:40
6085872
to
b52e60f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 21, 2024 14:28
b52e60f
to
0fb1a07
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 22, 2024 12:14
0fb1a07
to
7f039df
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:
^3.13.1
->^4.0.0
Release Notes
nodeca/js-yaml (js-yaml)
v4.1.0
Compare Source
Added
yaml.types.XXX
.options
property with original arguments kept as they were(see
yaml.types.int.options
as an example).Changed
Schema.extend()
now keeps old type order in case of conflicts(e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as
abcd
instead ofcbad
).v4.0.0
Compare Source
Changed
!!js/function
,!!js/regexp
,!!js/undefined
aremoved to js-yaml-js-types package.
safe*
functions. Useload
,loadAll
,dump
instead which are all now safe by default.
yaml.DEFAULT_SAFE_SCHEMA
andyaml.DEFAULT_FULL_SCHEMA
are removed, useyaml.DEFAULT_SCHEMA
instead.yaml.Schema.create(schema, tags)
is removed, useschema.extend(tags)
instead.!!binary
now always mapped toUint8Array
on load./lib
folder.01234
is now decimal,0o1234
is octal,1:23
is parsed as string instead of base60).dump()
no longer quotes:
,[
,]
,(
,)
except when necessary, #470, #557.(X:Y)
instead ofat line X, column Y
(also present in compact format), #332.dump()
now serializesundefined
asnull
in collections and removes keys withundefined
in mappings, #571.dump()
withskipInvalid=true
now serializes invalid items in collections as null.!
are now dumped as!tag
instead of!<!tag>
, #576.tag:yaml.org,2002:
are now shorthanded using!!
, #258.Added
.mjs
(es modules) support.quotingType
andforceQuotes
options for dumper to configurestring literal style, #290, #529.
styles: { '!!null': 'empty' }
option for dumper(serializes
{ foo: null }
as "foo:
"), #570.replacer
option (similar to option in JSON.stringify), #339.Tag
can now handle all tags or multiple tags with the same prefix, #385.Fixed
dump()
, #587.[foo,,bar]
) now throw an exceptioninstead of producing null, #321.
__proto__
key no longer overrides object prototype, #164.bower.json
.load()
and url-encoded indump()
(previously usage of custom non-ascii tags may have led to invalid YAML that can't be parsed).
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, 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.