chore(deps): bump ash from 3.0.2 to 3.0.7

[dependabot[bot]]

Bumps ash from 3.0.2 to 3.0.7.

Changelog

Sourced from ash's changelog.

v3.0.7 (2024-05-24)

Improvements:

• [identities] support nils_distinct? on identities

• [identties] support where option on identities

• [identities] allow calculations in identity keys

v3.0.6 (2024-05-23)

Bug Fixes:

• [policies] don't raise an error when authorizing against previous values without atomic upgrades

• [calculations] handle subquery-requiring calculations in calculate/2, ensuring we have a primary key

• [Ash.DataLayer] resolve mixup between atomic upsert vs update capability of datalayers (#1198)

v3.0.5 (2024-05-23)

Bug Fixes:

• [mix ash.*] only use Mix.deps_tree if defined (its only defined for elixir 1.15+)

Improvements:

• [atomic upgrade] add atomic_upgrade? flag to update/destroy actions

• [atomic upgrade] do not do atomic upgrade by default unless require_atomic? is true

• [atomic upgrade] allow configuring the read action used by atomic upgrades

v3.0.4 (2024-05-22)

Bug Fixes:

• [bulk update/destroy] ensure that all notifications are sent

3.0.3 (2024-05-22)

Features:

• [relationship pagination] allow retrieving the count of paginated relationships (#1183)

• [Ash.Reactor] Add bulk_create step type.

• [Ash.Reactor] Add bulk_update step type. (#1185)

Bug Fixes:

... (truncated)

Commits

• 65c0e81 chore: release version v3.0.7
• 3510cd4 chore: clean up changelog and format
• dc94f3a improvement: support nils_distinct? on identities
• 8b1ce5e chore: release version v3.0.6
• 808692b fix: improve non-atomic-upgrade policy handling
• e63d80e fix: handle subquery-requiring calculations in calculate/2
• d0ffc55 fix: mixup between atomic upsert vs update capability of datalayers (#1198)
• 969eee4 chore: release version v3.0.5
• feb187b improvement: add atomic_upgrade? flag to update/destroy actions
• 73a2ef4 fix: only use Mix.deps_tree if defined
• Additional commits viewable in compare view

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)