build(deps): bump jakarta.activation:jakarta.activation-api from 2.1.3 to 2.1.4

[dependabot]

Bumps jakarta.activation:jakarta.activation-api from 2.1.3 to 2.1.4.

Release notes

Sourced from jakarta.activation:jakarta.activation-api's releases.

Jakarta Activation 2.1.4 Final Release

The 2.1.4 release is a bug fix release of 2.1.x (Jakarta EE 10, Jakarta EE 11).

Following changes are included:

• moves resource file names from javax to jakarta namespace

Full Changelog: jakartaee/jaf-api@2.1.3...2.1.4

Commits

• 3dad341 Prepare release jakarta.activation:jakarta.activation-api:2.1.4
• 5f213b8 Rename resources so javax and jakarta can live in same classpath #174
• 510208a Merge pull request #155 from jakartaee/2.1.3-RELEASE
• e709bef Prepare next development cycle for 2.2.0-SNAPSHOT
• See full diff in compare view

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

[holgerfriedrich]

@dependabot rebase

[holgerfriedrich]

@jbonofre I assume that this was not yet there when you did the javax->jakarta transition. Shall we merge this minor version upgrade?

[jbonofre]

@holgerfriedrich yup, it makes total sense on main.

[holgerfriedrich]

@jbonofre I don't get why the artifacts (cache dir) are already gone. The build was just a few hour ago, the retention should be one day.
What is the global setting of the repo? As an open source project, we should not be affected by space limits. Or did you configure a repository limit?
You should be able to browse the stored artifacts in the repo settings.

If I now try to retrigger the failed test, it will not work -> so I have to rebuild the entire PR.

[jbonofre]

@holgerfriedrich let me check. It might be related to the number of concurrent jobs (across different PRs).

[holgerfriedrich]

@dependabot rebase