Update dependency me.friwi:jcefmaven to v132

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
me.friwi:jcefmaven	127.3.1 -> 132.3.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

jcefmaven/jcefmaven (me.friwi:jcefmaven)

v132.3.1: JCEF Maven 132.3.1

Compare Source

Update JCEF to 1770317

Build: GitHub Actions #​93
MVN version: 132.3.1
JCEF commit: 1770317
CEF version: 132.3.1+g144febe+chromium-132.0.6834.83

Use with Maven:

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcefmaven</artifactId>
    <version>132.3.1</version>
</dependency>

Natives (only include if you want to bundle them in a fat jar)

Linux AMD64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-linux-amd64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Linux ARM

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-linux-arm</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Linux ARM64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-linux-arm64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Macosx AMD64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-macosx-amd64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Macosx ARM64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-macosx-arm64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Windows AMD64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-windows-amd64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Windows ARM64

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-windows-arm64</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Windows i386

<dependency>
    <groupId>me.friwi</groupId>
    <artifactId>jcef-natives-windows-i386</artifactId>
    <version>jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83</version>
</dependency>

Use with Gradle:

implementation 'me.friwi:jcefmaven:132.3.1'

Natives (only include if you want to bundle them in a fat jar)

Linux AMD64

implementation 'me.friwi:jcef-natives-linux-amd64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Linux ARM

implementation 'me.friwi:jcef-natives-linux-arm:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Linux ARM64

implementation 'me.friwi:jcef-natives-linux-arm64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Macosx AMD64

implementation 'me.friwi:jcef-natives-macosx-amd64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Macosx ARM64

implementation 'me.friwi:jcef-natives-macosx-arm64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Windows AMD64

implementation 'me.friwi:jcef-natives-windows-amd64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Windows ARM64

implementation 'me.friwi:jcef-natives-windows-arm64:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Windows i386

implementation 'me.friwi:jcef-natives-windows-i386:jcef-1770317+cef-132.3.1+g144febe+chromium-132.0.6834.83'

Changes from previous release:

Update to CEF 132.3.1+g144febe+chromium-132.0.6834.83

Test results of this release
These test results are provided by developers like yourself. If the platform you are currently running on is marked as untested below, please consider submitting a test report. You can report your test results using a new issue in just a minute! It will help other developers in choosing a stable version. Thank you!

amd64
arm64
i386	-		-
arm		-	-

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.