Skip to content

build(deps): bump github.com/vapor/vapor from 4.102.1 to 4.106.2#19

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/swift/github.com/vapor/vapor-4.106.2
Closed

build(deps): bump github.com/vapor/vapor from 4.102.1 to 4.106.2#19
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/swift/github.com/vapor/vapor-4.106.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 4, 2024

Copy link
Copy Markdown
Contributor

Bumps github.com/vapor/vapor from 4.102.1 to 4.106.2.

Release notes

Sourced from github.com/vapor/vapor's releases.

4.106.1 - Omit ACAO header instead of empty value

What's Changed

Omit ACAO header instead of empty value by @​grahamburgsma in #3243

For context, Vapor currently sends an empty Access-Control-Allow-Origin (ACAO) header when the origin does not match or is set to none.

We recently had a pentest done against our Vapor server and the tester reported the following regarding the empty ACAO header:

When the header is empty, browsers might reject the request without detailed error messages, making it harder for developers to debug or even realize there is a problem. This lack of transparency can lead to extended periods of vulnerability before the issue is discovered.

Looking at some other sources as well, an empty header doesn’t appear to be a valid value and so could result in unexpected behaviour.

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#the_http_response_headers https://fetch.spec.whatwg.org/#http-access-control-allow-origin

This patch was released by @​0xTim

Full Changelog: vapor/vapor@4.106.0...4.106.1

4.105.2 - Raise error when the data expected an array but not parsed as array

What's Changed

Raise error when the data expected an array but not parsed as array by @​sidepelican in #3222

URLEncodedFormDecoder fails silently without throwing an error when attempting to decode data in the following pattern: array[0]=0&array[1]=1&array[3]=3. Now it is decoded as an empty array. Typically, a decoder throws an error when data cannot be parsed as the expected structure, so I propose modifying the decoder to throw an error in this case as well.

Reviewers

Thanks to the reviewers for their help:

This patch was released by @​ptoffy

Full Changelog: vapor/vapor@4.105.1...4.105.2

4.105.1 - Throw an error if unkeyed container is at end

What's Changed

Throw an error if unkeyed container is at end by @​supersonicbyte in #3226

Throwing an error if the unkeyed container is at end while decoding query params fixes the crash mentioned with this issue: vapor/vapor#3217

The error being thrown is DecodingError.valueNotFound and it’s matching the error thrown by JSONDecoder.

New Contributor

... (truncated)

Commits

Dependabot compatibility score

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 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 <dependency name> 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)

Bumps [github.com/vapor/vapor](https://github.com/vapor/vapor) from 4.102.1 to 4.106.2.
- [Release notes](https://github.com/vapor/vapor/releases)
- [Commits](vapor/vapor@4.102.1...4.106.2)

---
updated-dependencies:
- dependency-name: github.com/vapor/vapor
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 4, 2024
@dependabot @github

dependabot Bot commented on behalf of github Nov 11, 2024

Copy link
Copy Markdown
Contributor Author

Superseded by #20.

@dependabot dependabot Bot closed this Nov 11, 2024
@dependabot dependabot Bot deleted the dependabot/swift/github.com/vapor/vapor-4.106.2 branch November 11, 2024 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants