-
Notifications
You must be signed in to change notification settings - Fork 4
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 #467
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/js-yaml-4.x
base: develop
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
from
January 5, 2021 23:46
16a5e6f
to
edd8104
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
January 18, 2021 18:12
edd8104
to
2e522c9
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
16 times, most recently
from
February 15, 2021 23:05
afe3419
to
2bc9753
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
8 times, most recently
from
February 23, 2021 00:41
9f2c51a
to
1b434da
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
3 times, most recently
from
March 1, 2021 23:29
4106ba2
to
4ebefdf
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
7 times, most recently
from
September 1, 2021 01:03
4b57cc8
to
c249917
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
4 times, most recently
from
September 12, 2021 09:50
cf9d166
to
9b68729
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
6 times, most recently
from
September 17, 2021 00:11
3a8abf7
to
0d5e6f0
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 23, 2021 00:08
0d5e6f0
to
4ce1975
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
March 26, 2022 14:57
4ce1975
to
6fd183f
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 25, 2022 15:48
6fd183f
to
676a6e1
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 20, 2022 11:52
676a6e1
to
2e402c7
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
September 15, 2023 21:50
2e402c7
to
6adbb47
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 10, 2023 23:11
6adbb47
to
1811646
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
October 18, 2023 07:13
1811646
to
456334d
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 7, 2023 21:19
456334d
to
6f013c6
Compare
renovate
bot
force-pushed
the
renovate/js-yaml-4.x
branch
from
November 9, 2023 17:25
6f013c6
to
785436b
Compare
renovate
bot
changed the title
fix(deps): update dependency js-yaml to v4
fix(deps): update dependency js-yaml to v4 - abandoned
Dec 8, 2024
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
renovate
bot
changed the title
fix(deps): update dependency js-yaml to v4 - abandoned
fix(deps): update dependency js-yaml to v4
Dec 8, 2024
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
3.12.7
->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: Enabled.
♻ 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.