CLDR-15970 j:(deps): Bump microprofile from 3.3 to 6.0 in /tools

[dependabot]

Bumps microprofile from 3.3 to 6.0.

Release notes

Sourced from microprofile's releases.

6.0

Spec PDF | Spec HTML

MicroProfile 6.0 aligns with Jakarta EE 10 Core Profile and replaces MicroProfile OpenTracing with MicroProfile Telemetry. This release continues the Jakarta EE 9.1 jakarta.* namespace alignment with Jakarta specifications introduced in MicroProfile 5.0.

Based on MicroProfile's time-boxed release process, this is a major release that includes the following updates:

• Jakarta EE 10 Core Profile
• MicroProfile Config 3.0
• MicroProfile Health 4.0
• MicroProfile Fault Tolerance 4.0
• MicroProfile JWT RBAC 2.1
• MicroProfile Metrics 5.0
• MicroProfile OpenAPI 3.1
• MicroProfile Telemetry 1.0
• MicroProfile Rest Client 3.0

To get started with MicroProfile 6.0, add the following dependency to your pom.xml to get the complete MicroProfile stack:

<dependency>
    <groupId>org.eclipse.microprofile</groupId>
    <artifactId>microprofile</artifactId>
    <version>6.0</version>
    <type>pom</type>
    <scope>provided</scope>
</dependency>

6.0-RC3

Spec PDF | Spec HTML

MicroProfile 6.0-RC3 aligns with Jakarta EE 10 Core Profile and replaces MicroProfile OpenTracing with MicroProfile Telemetry. This release continues the Jakarta EE 9.1 jakarta.* namespace alignment with Jakarta specifications introduced in MicroProfile 5.0.

Based on MicroProfile's time-boxed release process, this is a major release that includes the following updates:

• Jakarta EE 10 Core Profile
• MicroProfile Config 3.0
• MicroProfile Health 4.0
• MicroProfile Fault Tolerance 4.0
• MicroProfile JWT RBAC 2.1
• MicroProfile Metrics 5.0
• MicroProfile OpenAPI 3.1
• MicroProfile Telemetry 1.0
• MicroProfile Rest Client 3.0

To get started with MicroProfile 6.0-RC3, add the following dependency to your pom.xml to get the complete MicroProfile stack:

<dependency>
    <groupId>org.eclipse.microprofile</groupId>
    <artifactId>microprofile</artifactId>
</tr></table> 

... (truncated)

Commits

• d9cbcb2 [maven-release-plugin] prepare release 6.0
• c5eefbd [maven-release-plugin] prepare for next development iteration
• f27975d [maven-release-plugin] prepare release 6.0-RC4
• 95bbad5 Mp 6 additional issues (#300)
• 9fec2d3 MP 6 Issues PR (#298)
• 4edb7df [maven-release-plugin] prepare for next development iteration
• a6a9f65 [maven-release-plugin] prepare release 6.0
• 9c1dd53 Final tidyup for MP 6.0 release (#282)
• 59d68a9 [maven-release-plugin] prepare for next development iteration
• 6af8b92 [maven-release-plugin] prepare release 6.0-RC3
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Dependabot tried to add @btangmu and @srl295 as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/naotoj/cldr/pulls/57/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the naotoj/cldr repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

[dependabot]

Superseded by #86.