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

build(deps): bump iot-device-client from 2.1.5 to 2.2.0 #981

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 7, 2023

Bumps iot-device-client from 2.1.5 to 2.2.0.

Release notes

Sourced from iot-device-client's releases.

Azure IoT SDK for Java LTS Release 2021-6-17

This release is an LTS release. See here for more details on what this means

Java Deps (com.microsoft.azure.sdk.iot:iot-deps:0.14.0)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)
  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Java IotHub Device Client (com.microsoft.azure.sdk.iot:iot-device-client:1.31.0)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)
  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Java IotHub Service Client (com.microsoft.azure.sdk.iot:iot-service-client:1.32.0)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)
  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Bug fixes

  • Fixed a bug where subsequent calls to receive file upload notifications and feedback messages failed (#1238)

Java Provisioning Device Client (com.microsoft.azure.sdk.iot.provisioning:provisioning-device-client:1.9.0)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)
  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Java Provisioning Service Client (com.microsoft.azure.sdk.iot.provisioning:provisioning-service-client:1.8.0)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)
  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Java X509 Provider (com.microsoft.azure.sdk.iot.provisioning.security:x509-provider:1.1.6)

  • Increase dependency versions for bouncycastle to 1.69 (#1245)

Java Security Provider (com.microsoft.azure.sdk.iot.provisioning.security:security-provider:1.5.0)

  • Add new Digicert Global Root G2 certificate to trusted root chain (#1247)

Note that this release is the first release where all the packages will be compatible with both the current IoT Hub public certificate (which is being phased out) and compatible with the new IoT Hub public certificate that will be arriving June 2022.

More information about this upcoming change in IoT Hub and DPS certificate roots can be seen here: https://techcommunity.microsoft.com/t5/internet-of-things/azure-iot-tls-critical-changes-are-almost-here-and-why-you/ba-p/2393169

https://search.maven.org/artifact/com.microsoft.azure.sdk.iot/iot-device-client/1.31.0/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot/iot-service-client/1.32.0/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot/iot-deps/0.14.0/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot.provisioning/provisioning-device-client/1.9.0/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot.provisioning/provisioning-service-client/1.8.0/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot.provisioning.security/x509-provider/1.1.6/jar https://search.maven.org/artifact/com.microsoft.azure.sdk.iot.provisioning.security/security-provider/1.2.0/jar

... (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 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 [iot-device-client](https://github.com/Azure/azure-iot-sdk-java) from 2.1.5 to 2.2.0.
- [Release notes](https://github.com/Azure/azure-iot-sdk-java/releases)
- [Changelog](https://github.com/Azure/azure-iot-sdk-java/blob/main/upcoming_certificate_changes_readme.md)
- [Commits](https://github.com/Azure/azure-iot-sdk-java/commits)

---
updated-dependencies:
- dependency-name: com.microsoft.azure.sdk.iot:iot-device-client
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jun 7, 2023
@sruehl sruehl merged commit 29efaa4 into develop Jun 7, 2023
@sruehl sruehl deleted the dependabot/maven/com.microsoft.azure.sdk.iot-iot-device-client-2.2.0 branch June 7, 2023 07:43
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 java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant