Skip to content

build(deps): bump nebulex from 2.6.5 to 3.0.0#498

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/hex/nebulex-3.0.0
Open

build(deps): bump nebulex from 2.6.5 to 3.0.0#498
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/hex/nebulex-3.0.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 24, 2026

Bumps nebulex from 2.6.5 to 3.0.0.

Release notes

Sourced from nebulex's releases.

v3.0.0

To see what's new, check the CHANGELOG

v3.0.0-rc.2

To see what's new, check the CHANGELOG

v3.0.0-rc.1

To see what's new, check the CHANGELOG

v2.6.6

To see what's new, check the CHANGELOG

Changelog

Sourced from nebulex's changelog.

v3.0.0 (2026-02-21)

Full Changelog

Enhancements

  • [Nebulex.Caching.Decorators] Decorator-invoked cache operations (cacheable, cache_put, cache_evict) now automatically inject the :decorator_context into the :telemetry_metadata option. This enables telemetry handlers to identify which decorated function triggered each cache operation. The :decorator_context map includes :decorator, :module, :function_name, and :arity. #251.
  • [Nebulex.Caching.Decorators] The cache_evict decorator now properly passes opts through all eviction paths (delete, delete_all), ensuring telemetry metadata propagates consistently.
  • [Nebulex.Adapter] The :telemetry_metadata and :telemetry_event options are now extracted from opts before passing them to the adapter callback, keeping adapter args clean.
  • [Nebulex.Caching.Decorators] Added :transaction option to wrap decorated function execution and cache operations in a cache transaction. When set to true, the decorator locks the specified cache keys for the duration of the transaction, preventing concurrent processes from accessing or modifying them simultaneously. The transaction intelligently determines which keys to lock based on the decorator options (e.g., key: {:in, keys}, :query, or generated keys). This feature helps prevent race conditions, cache stampede, and inconsistent updates in concurrent environments. The :transaction option can be configured both at the module level (use Nebulex.Caching) and at the decorator level, with decorator-level settings overriding module-level defaults. #248.
  • [Nebulex.Adapters.Coherent] Added new coherent cache adapter to nebulex_distributed. The coherent adapter provides a "local cache with distributed invalidation" pattern where each node maintains its own independent local cache, but writes trigger invalidation events across the cluster via Nebulex.Streams. Key features include maximum read performance (pure local lookups), distributed invalidation via Phoenix.PubSub, and a write-invalidate protocol that minimizes network overhead by only broadcasting invalidation events. Ideal for read-heavy workloads, configuration/reference data caching, and session caches.
  • [Documentation] Overall documentation improvements.

Backwards incompatible changes

  • [Nebulex.Adapter.Transaction] The default transaction implementation has been removed from the core Nebulex library. Each adapter is now responsible for providing its own transaction implementation tailored to its specific needs. This change keeps the core library more generic and allows adapters to optimize transaction handling for their particular use cases (e.g., local ETS-based locking for single-node caches vs. distributed locking for multi-node setups). Adapters that support transactions must implement

... (truncated)

Commits
  • bbea8bd chore(release): v3.0.0 🚀
  • 8c3a852 docs: fix typos, grammar, and code examples across guides and modules
  • b173a22 feat(caching): add decorator context to telemetry metadata (#251)
  • 48ea030 docs(workflow): add agent workflow and contribution guidelines
  • 3f6148c chore(gitignore): update ignore rules
  • d0483fd Update docs
  • dec61b9 refactor(caching): split decorators internals into Context/Runtime modules
  • 7e9d7e5 Overall updates and enhancements
  • 3f1d374 Update docs and guides
  • 6d0672a Fix the target type for the Nebulex.Event.CacheEntryEvent
  • 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 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)

Bumps [nebulex](https://github.com/elixir-nebulex/nebulex) from 2.6.5 to 3.0.0.
- [Release notes](https://github.com/elixir-nebulex/nebulex/releases)
- [Changelog](https://github.com/elixir-nebulex/nebulex/blob/main/CHANGELOG.md)
- [Commits](elixir-nebulex/nebulex@v2.6.5...v3.0.0)

---
updated-dependencies:
- dependency-name: nebulex
  dependency-version: 3.0.0
  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 elixir Pull requests that update Elixir code labels Feb 24, 2026
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 elixir Pull requests that update Elixir code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants