Skip to content

build(deps): Bump javax.enterprise:cdi-api from 1.2 to 2.0.SP1#788

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/maven/javax.enterprise-cdi-api-2.0.SP1
Open

build(deps): Bump javax.enterprise:cdi-api from 1.2 to 2.0.SP1#788
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/maven/javax.enterprise-cdi-api-2.0.SP1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 6, 2026

Bumps javax.enterprise:cdi-api from 1.2 to 2.0.SP1.

Release notes

Sourced from javax.enterprise:cdi-api's releases.

CDI 2.0.SP1 release

CDI version including privileged block to allow CDI to play nice wit security manager

CDI 2.0 release

Release for Java EE 8

Commits
  • 676366d Prepare for 2.0.SP1 release
  • ce2e73c CDI-727 CDI.current() should use privileged block (#391)
  • 0c323bb CDI-699 AnnotationLiteral should use privileged actions for reflective operat...
  • 9f5eaad Surefire config simplification by overriding default-test suite
  • c9aedea Add a test suite running with security manager and a policy
  • eb56bf4 Update Asccidoctor Ruby dependencies to prevent security issue
  • d7f152f Add License.txt to confirm Red Hat policy
  • 4d2392a Update TCK version to latest final for spec with assertion generation
  • ebe752e Generate a nice TOC using tocify (#389)
  • 4a4693c Better config for spec with assertion generation
  • Additional commits viewable in compare view

Dependabot compatibility score

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

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

Bumps [javax.enterprise:cdi-api](https://github.com/cdi-spec/cdi) from 1.2 to 2.0.SP1.
- [Release notes](https://github.com/cdi-spec/cdi/releases)
- [Commits](jakartaee/cdi@1.2...2.0.SP1)

---
updated-dependencies:
- dependency-name: javax.enterprise:cdi-api
  dependency-version: 2.0.SP1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

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 Jan 6, 2026
@rhusar
Copy link
Member

rhusar commented Feb 17, 2026

@jamezp What do you think about this one? This is Java EE 7 to Java EE 8 upgrade. Tests pass, scope is provided. Only thing that comes to mind is If if tests run against Java EE 7 app servers, having CDI 2.0 as the compile dependency could cause issues if CDI 2.0-specific APIs are used?

@rhusar rhusar requested a review from jamezp February 17, 2026 09:30
@jamezp
Copy link
Member

jamezp commented Feb 17, 2026

@rhusar That is a great question. I wonder if we should consider dropping it or creating a branch in https://github.com/arquillian/arquillian-jakarta for EE 8 only and just drop EE 7 support. Then we could simply remove these modules from this repository.

WDYT?

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.

2 participants

Comments