chore(deps): bump org.jboss.weld:weld-core-parent from 4.0.3.Final to 6.0.0.Final in /jans-config-api

[dependabot]

Bumps org.jboss.weld:weld-core-parent from 4.0.3.Final to 6.0.0.Final.

Commits

• eb8de65 [maven-release-plugin] prepare release 6.0.0.Final
• 1ed5ef1 Trigger Weld 6.0.0.Final release
• 0dbecdc Upgrade Weld API to Final artifact
• a68b067 [maven-release-plugin] prepare for next development iteration
• 09939c4 [maven-release-plugin] prepare release 6.0.0.CR2
• 7983a58 Trigger release for 6.0.0.CR2
• de7a926 WELD-2804 Remove deprecated code parts.
• 8b57e0f WELD-2803 Remove WeldCrossContextFilter
• 23f8e2f [maven-release-plugin] prepare for next development iteration
• d6da8f4 [maven-release-plugin] prepare release 6.0.0.CR1
• Additional commits viewable in compare view

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)

[dryrunsecurity]

DryRun Security Summary

The pull request updates the Weld dependency version from 4.0.3.Final to 6.0.0.Final in the jans-config-api/pom.xml file, potentially bringing new features, bug fixes, and performance improvements to the project's CDI implementation.

Expand for full summary

Summary:

The code change in this pull request updates the Weld dependency version from 4.0.3.Final to 6.0.0.Final in the jans-config-api/pom.xml file. Weld is a Java EE and Jakarta EE implementation of the CDI (Contexts and Dependency Injection) specification, which is a key part of the Java EE/Jakarta EE platform. Updating the Weld version likely brings in new features, bug fixes, and performance improvements to the CDI implementation used in the jans-config-api project.

From an application security perspective, this change is not particularly noteworthy, as dependency updates are a routine part of software maintenance and do not necessarily introduce security concerns on their own. However, it's always a good practice to review the release notes and change logs of any major dependency updates to ensure there are no known security vulnerabilities or breaking changes that could impact the application. Additionally, it's recommended to have a comprehensive test suite that covers the application's core functionality and to run those tests after any dependency updates to ensure the application continues to function as expected.

Files Changed:

• jans-config-api/pom.xml: This file has been updated to change the Weld dependency version from 4.0.3.Final to 6.0.0.Final. Weld is a Java EE and Jakarta EE implementation of the CDI (Contexts and Dependency Injection) specification, which is a key part of the Java EE/Jakarta EE platform. Updating the Weld version likely brings in new features, bug fixes, and performance improvements to the CDI implementation used in the jans-config-api project.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.