Skip to content
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

Bump @cap-js-community/odata-v2-adapter from 1.10.6 to 1.11.3 #536

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 3, 2023

Bumps @cap-js-community/odata-v2-adapter from 1.10.6 to 1.11.3.

Release notes

Sourced from @​cap-js-community/odata-v2-adapter's releases.

v1.11.3

Fix absolute OData V4 paths for $batch calls

v1.11.2

Fix metadata request for absolute OData V4 paths

v1.11.1

Protocol Compatibility Fix

v1.11.0

  • CDS 7
Changelog

Sourced from @​cap-js-community/odata-v2-adapter's changelog.

Version 1.11.3 - 2023-07-03

Fixed

  • Fix absolute OData V4 paths for $batch calls

Version 1.11.2 - 2023-07-03

Fixed

  • Fix $metadata request for absolute OData V4 paths

Version 1.11.1 - 2023-06-27

Fixed

  • Fix compatibility for option middlewares disabled or feature serve_on_root enabled

Version 1.11.0 - 2023-06-26

Added

  • CDS 7 support
  • Default route with CDS < 7 or option middlewares disabled or feature serve_on_root enabled stays v2
  • Default route with CDS >= 7 is /odata/v2
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 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 [@cap-js-community/odata-v2-adapter](https://github.com/cap-js-community/odata-v2-adapter) from 1.10.6 to 1.11.3.
- [Release notes](https://github.com/cap-js-community/odata-v2-adapter/releases)
- [Changelog](https://github.com/cap-js-community/odata-v2-adapter/blob/main/CHANGELOG.md)
- [Commits](cap-js-community/odata-v2-adapter@v1.10.6...v1.11.3)

---
updated-dependencies:
- dependency-name: "@cap-js-community/odata-v2-adapter"
  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 Jul 3, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 3, 2023

Looks like @cap-js-community/odata-v2-adapter is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jul 3, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/cap-js-community/odata-v2-adapter-1.11.3 branch July 3, 2023 14:06
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