-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(deps): update dependency js-yaml to v4 #462
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.
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
11 times, most recently
from
January 30, 2021 12:00
ce5862b
to
a806261
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
7 times, most recently
from
February 10, 2021 22:08
f0a991d
to
4d331e8
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
February 19, 2021 22:21
9f105d0
to
5b00e9c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
March 1, 2021 01:10
a4fd1fc
to
38b556c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
March 8, 2021 01:57
72279ac
to
59632c7
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
October 11, 2021 02:41
fcb7188
to
685a82a
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 11, 2021 03:58
685a82a
to
df37465
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
October 23, 2021 02:47
508fc39
to
a3b4b83
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 9, 2021 22:10
a3b4b83
to
d7febc5
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
November 19, 2021 19:41
ada4826
to
1cf3a86
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
June 24, 2022 05:33
9229eea
to
084150e
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
July 5, 2022 18:53
084150e
to
c8a32df
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 20, 2022 18:14
c8a32df
to
01743fa
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
6 times, most recently
from
March 25, 2023 04:34
d07a3b0
to
aac992a
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 4, 2023 19:55
aac992a
to
82e51b0
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 15, 2023 21:15
82e51b0
to
223d54b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
October 17, 2023 22:18
fdef32f
to
263f16f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
October 23, 2023 19:59
00c6465
to
8b6f37d
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 7, 2023 23:37
8b6f37d
to
041c37c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
January 31, 2024 21:23
041c37c
to
6c686c9
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
February 1, 2024 01:57
6c686c9
to
2209790
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.14.1
->4.1.0
3.12.10
->4.0.9
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 - 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.