search

apache / shiro

Apache Shiro
https://shiro.apache.org/
Apache License 2.0
4.31k stars 2.31k forks source link

chore(deps): bump com.hazelcast:hazelcast from 3.12.13 to 4.0 #1731

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps com.hazelcast:hazelcast from 3.12.13 to 4.0.

Release notes

Sourced from com.hazelcast:hazelcast's releases.

4.0

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast IMDG 4.0, Open Source edition release.

NOTE: See the Hazelcast IMDG 4.0 Migration Guide for the detailed guidelines to be followed when upgrading to Hazelcast IMDG 4.0.

New Features

Hazelcast IMDG Enterprise New Features:

  • Persistent Memory Integration: Added support for persistent memory, such as Intel(R) Optane(TM) DC, to be used by Hazelcast's High-Density Memory Store feature. See the Using Persistent Memory section.

  • Encrypting Data in Hot Restart Store: Provided a framework and implementation to encrypt data in Hot Restart stores ("at rest") for data held in distributed structures. See the Encryption at Rest section.

  • X.509 Certificate Authentication: Added support for credential retrieval by the members from the X.509 certificates configured on the clients. See the Security chapter.

  • Out of the Box LDAP Configuration: Introduced a new LDAP login module where you do not need to provide your own JAAS login module for this purpose. See the Security chapter.

  • CP Subsystem Persistence: Implemented persistency for Hazelcast's CP (Consistency & Partition Tolerance) subsystem. See the CP Subsystem Persistence section.

Hazelcast IMDG Open Source New Features:

  • CP Subsystem Development Mode: Introduced UNSAFE mode for the CP data structures. This way, you do not need to have at least three IMDG members to use CP subsystem: you can benefit from its functionalities using only one or two members. See the CP Subsystem Unsafe Mode section.

  • Bitmap Indexes: Introduced this feature to significantly lower index memory usage for low-cardinality columns and also to speed up the queries and lower memory requirements for them when the queries have multiple predicates acting on the same bitmap index. Note that bitmap indexes usage, currently, is a good fit for array/collection attribute indexing, rather than regular single-valued attributes. See the Bitmap Indexes section.

Enhancements

Hazelcast IMDG Enterprise Enhancements:

  • Separating WAN Publisher Configuration: The previously known wan-publisher (or WanPublisherConfig) has been separated into two configuration elements to be used for built-in and custom WAN publishers:

  • Tracking WAN Synchronization Events: Management Center, logs and diagnostics now report the progress of a WAN synchronization. #15221

  • Improvements in the JAAS Authentication Mechanism:

    • Aligned with JAAS best practices.
    • Added support for the standard JAAS callbacks, i.e., NameCallback and PasswordCallback
    • Avoided automatic deserialization of custom credentials in the client protocol.
    • Introduce the concept of security roles to distinguish between (a single) connecting side identity and its privileges.
    • Used Credentials object only for authentication to prevent secrets leaks.
    • Cleaned up the Credentials interface. See the JAAS Authentication section.

  • Improvements in the Security Configuration:

    • Replaced the <group> configuration by simple <cluster-name>.
    • Removed the group-password configuration.
    • Introduced the concept of security realms on the members. #15651

... (truncated)

Commits
  • 8b959f5 Don't exclude buildutils JavaDoc in release profile
  • d9f6191 Final touches to the IMDG OS 4.0 release notes.
  • 4be6b5d Update Hazelcast Kubernetes plugin (#16592)
  • e003b39 Adding IMDG OS 4.0 release notes.
  • 6fe7eaa Remove community license (#16573)
  • 31cc8a6 4.0
  • 69dc21a Support bitmap indexes in client protocol (#16555)
  • fa9d0b5 Fixes NPE when completing exceptionally in ExecutorService
  • a102541 Fix flaky ManagementCenterServiceIntegrationTest (#16563)
  • 4ec475b [Revert] Make the Client ProxyManager not listen to the distributed object ev...
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
dependabot[bot] commented 1 week ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.