-
Notifications
You must be signed in to change notification settings - Fork 0
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 #40
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
2 times, most recently
from
January 5, 2021 03:15
a9c9b0b
to
8faf425
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
January 18, 2021 17:57
5f385e1
to
b32b873
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
January 20, 2021 21:06
b32b873
to
cc17158
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
February 10, 2021 23:04
f8c0596
to
111a1d0
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
February 19, 2021 09:25
32c3950
to
e74743f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
February 20, 2021 19:48
cb1d84a
to
e1c7f21
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
March 16, 2021 02:23
23869aa
to
22494a9
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
March 27, 2021 06:11
22494a9
to
e57611a
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
5 times, most recently
from
April 16, 2021 11:15
f32d3e5
to
62f1e5e
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
April 27, 2021 18:13
62f1e5e
to
a79c91b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
May 5, 2021 01:46
a79c91b
to
c8f76a3
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
May 14, 2021 10:16
286bdc4
to
61dd192
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
May 21, 2021 22:58
5ee74a7
to
4a1426b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
June 2, 2021 11:14
7d89dfc
to
9c38744
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
June 8, 2021 01:37
9c38744
to
ccfd00b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
June 17, 2021 01:44
ccfd00b
to
3fd69aa
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
July 7, 2021 18:34
8a611b3
to
d48b30a
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
July 24, 2021 20:51
d48b30a
to
6b551ab
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
August 4, 2021 18:42
2f79820
to
540cd07
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
August 9, 2021 01:39
540cd07
to
5fb72f1
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
5 times, most recently
from
August 26, 2021 03:20
d5682e6
to
b958798
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
August 31, 2021 18:35
b958798
to
b471896
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 1, 2021 01:53
b471896
to
d666d78
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.14.1
->4.1.0
Release Notes
nodeca/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: 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 has been generated by WhiteSource Renovate. View repository job log here.