-
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 #187
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
requested review from
a team,
marekweb and
tjkandala
and removed request for
a team
January 7, 2021 16:49
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
January 22, 2021 16:59
c1a3d14
to
15b6148
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
February 11, 2021 18:08
15b6148
to
27c88b8
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
April 14, 2021 21:42
27c88b8
to
2829b85
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
April 23, 2021 15:34
2829b85
to
a9fe47f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
July 6, 2021 22:16
a9fe47f
to
7bff15f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
August 20, 2021 18:47
7bff15f
to
916b480
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 22, 2021 23:09
916b480
to
99cb047
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 19, 2021 19:18
99cb047
to
242fc69
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
June 19, 2022 03:32
242fc69
to
a9f814b
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
August 5, 2022 01:32
a9f814b
to
551c791
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 1, 2022 13:16
551c791
to
03e8f97
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 1, 2022 10:02
03e8f97
to
35b8f05
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
November 8, 2022 02:26
3bba92a
to
555713c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
December 1, 2022 11:44
555713c
to
6b5ee34
Compare
renovate
bot
changed the title
fix(deps): update dependency js-yaml to v4
Update dependency js-yaml to v4
Dec 17, 2022
renovate
bot
changed the title
Update dependency js-yaml to v4
fix(deps): update dependency js-yaml to v4
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
January 25, 2023 12:14
6b5ee34
to
6164cc9
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
February 1, 2023 16:21
6164cc9
to
78c7989
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
March 1, 2023 13:12
e7c39ab
to
2076c3d
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 15, 2023 23:32
2076c3d
to
3df47eb
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 10, 2023 19:47
3df47eb
to
7f89554
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 18, 2023 07:05
7f89554
to
7086856
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
2 times, most recently
from
November 7, 2023 22:26
4351acb
to
b98a14c
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 8, 2023 02:12
b98a14c
to
75804d3
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.0
->^4.1.0
3.12.5
->4.0.9
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
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).
v3.14.1
Compare Source
Security
.load()
(in &anchor).Configuration
📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, 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.
🔕 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.