Bump undertow-core from 2.2.19.Final to 2.2.20.Final#557
Merged
mergify[bot] merged 1 commit intomainfrom Oct 10, 2022
Merged
Conversation
Bumps [undertow-core](https://github.com/undertow-io/undertow) from 2.2.19.Final to 2.2.20.Final. - [Release notes](https://github.com/undertow-io/undertow/releases) - [Commits](undertow-io/undertow@2.2.19.Final...2.2.20.Final) --- updated-dependencies: - dependency-name: io.undertow:undertow-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
robfrank
approved these changes
Oct 10, 2022
dependabot
Bot
deleted the
dependabot/maven/io.undertow-undertow-core-2.2.20.Final
branch
mergify Bot
added a commit
that referenced
this pull request
Nov 19, 2025
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.14.1 to 3.14.2. Changelog *Sourced from [js-yaml's changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md).* > [3.14.2] - 2025-11-15 > --------------------- > > ### Security > > * Backported v4.1.1 fix to v3 > > [4.1.1] - 2025-11-12 > -------------------- > > ### Security > > * Fix prototype pollution issue in yaml merge (<<) operator. > > [4.1.0] - 2021-04-15 > -------------------- > > ### Added > > * Types are now exported as `yaml.types.XXX`. > * Every type now has `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 of `cbad`). > > [4.0.0] - 2021-01-03 > -------------------- > > ### Changed > > * Check [migration guide](https://github.com/nodeca/js-yaml/blob/master/migrate_v3_to_v4.md) to see details for all breaking changes. > * Breaking: "unsafe" tags `!!js/function`, `!!js/regexp`, `!!js/undefined` are > moved to [js-yaml-js-types](https://github.com/nodeca/js-yaml-js-types) package. > * Breaking: removed `safe*` functions. Use `load`, `loadAll`, `dump` > instead which are all now safe by default. > * `yaml.DEFAULT_SAFE_SCHEMA` and `yaml.DEFAULT_FULL_SCHEMA` are removed, use > `yaml.DEFAULT_SCHEMA` instead. > * `yaml.Schema.create(schema, tags)` is removed, use `schema.extend(tags)` instead. > * `!!binary` now always mapped to `Uint8Array` on load. > * Reduced nesting of `/lib` folder. > * Parse numbers according to YAML 1.2 instead of YAML 1.1 (`01234` is now decimal, > `0o1234` is octal, `1:23` is parsed as string instead of base60). > * `dump()` no longer quotes `:`, `[`, `]`, `(`, `)` except when necessary, [#470](https://redirect.github.com/nodeca/js-yaml/issues/470), [#557](https://redirect.github.com/nodeca/js-yaml/issues/557). > * Line and column in exceptions are now formatted as `(X:Y)` instead of > `at line X, column Y` (also present in compact format), [#332](https://redirect.github.com/nodeca/js-yaml/issues/332). > * Code snippet created in exceptions now contains multiple lines with line numbers. > * `dump()` now serializes `undefined` as `null` in collections and removes keys with > `undefined` in mappings, [#571](https://redirect.github.com/nodeca/js-yaml/issues/571). > * `dump()` with `skipInvalid=true` now serializes invalid items in collections as null. > * Custom tags starting with `!` are now dumped as `!tag` instead of `!<!tag>`, [#576](https://redirect.github.com/nodeca/js-yaml/issues/576). > * Custom tags starting with `tag:yaml.org,2002:` are now shorthanded using `!!`, [#258](https://redirect.github.com/nodeca/js-yaml/issues/258). > > ### Added > > * Added `.mjs` (es modules) support. > * Added `quotingType` and `forceQuotes` options for dumper to configure > string literal style, [#290](https://redirect.github.com/nodeca/js-yaml/issues/290), [#529](https://redirect.github.com/nodeca/js-yaml/issues/529). > * Added `styles: { '!!null': 'empty' }` option for dumper > (serializes `{ foo: null }` as "`foo:` "), [#570](https://redirect.github.com/nodeca/js-yaml/issues/570). ... (truncated) Commits * [`9963d36`](nodeca/js-yaml@9963d36) 3.14.2 released * [`10d3c8e`](nodeca/js-yaml@10d3c8e) dist rebuild * [`5278870`](nodeca/js-yaml@5278870) fix prototype pollution in merge (<<) ([#731](https://redirect.github.com/nodeca/js-yaml/issues/731)) * See full diff in [compare view](nodeca/js-yaml@3.14.1...3.14.2) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/ArcadeData/arcadedb/network/alerts).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps undertow-core from 2.2.19.Final to 2.2.20.Final.
Commits
d0d56e8Prepare 2.2.20.Final2343d72Merge pull request #1376 from fl4via/2.2.x_backport_bug_fixes843a057UNDERTOW-2109 create large file in expected locationdfc0b82UNDERTOW-2142 ChunkedStreamSinkConduit.write writes all requested buffers1fd2d08[UNDERTOW-2140] add TLS 1.3 ciphers and re-arrange match rulesc408150UNDERTOW-2145 OutputStreams only awaitWritable after a write returns zero6b12248[UNDERTOW-2159] add null check to SessionManagera02d6bbMerge pull request #1370 from aogburn/032938728d1b342[UNDERTOW-2147] fix race condition between session changeSessionId and invali...e5d70dbNext is 2.2.20.FinalDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)