chore(deps): update dependency ash to v3.37.2 [security] #638

Closed
renovate wants to merge 1 commit from renovate/hex-ash-vulnerability into main
Collaborator

This PR contains the following updates:

Package Type Update Change
ash (source) prod minor 3.36.1 → 3.37.2

Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records

CVE-2026-114214 / EEF-CVE-2026-114214 / GHSA-g2h4-xp57-q863

More information

Details

Summary

Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.

When a has_many relationship declared with through: was loaded for a single record with a limit of 1, or an unsorted has_one through relationship was loaded with a limit of 1, lateral_join?/4 in lib/ash/actions/read/relationships.ex chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an offset. The read still runs the destination's policies but carries the relationship as accessing_from, so a client paging such a field (for example teachers(limit: 1, offset: n) through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.

This issue affects ash: from 3.24.0 before 3.37.1.

Impact

A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship.

Configurations

Reachable when a through relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource's read policies rely on the relationship (accessing_from) or are otherwise open to the caller.

Severity

  • CVSS Score: 6.0 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV.


An upsert on the primary key in Ash ignores attribute multitenancy, so one tenant can read, overwrite and take over another tenant's records

CVE-2026-96581 / EEF-CVE-2026-96581 / GHSA-vw7c-67pf-gh96

More information

Details

Summary

Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take over another tenant's records via an upserting create action.

Under attribute multitenancy, Ash.Actions.Create (lib/ash/actions/create/create.ex) and Ash.Actions.Create.Bulk (lib/ash/actions/create/bulk.ex) upserted on the primary key, or on an all_tenants? identity, without scoping the conflicting record to the request's tenant. A caller of a create action with upsert? true that accepts the primary key, supplying a record id from another tenant, updated that record's upsert fields and received all of its attributes in the result. With the default upsert fields the tenant attribute was written too, moving the record into the caller's tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller's own.

This issue affects ash: from 1.22.0 before 3.37.2.

Impact

A signed-in user of one tenant posts another tenant's record id to an upserting create action, receives that record's attributes, overwrites its upsert fields, and with the default upsert fields moves it into their own tenant.

Workarounds

Add upsert_condition expr(<tenant attribute> == ^tenant()) to every create action that upserts on the primary key or on an all_tenants? identity, and do not combine it with return_skipped_upsert?. An upsert into another tenant's record then fails with Ash.Error.Changes.StaleRecord (or is skipped in a bulk create) and leaves that record unchanged. This does not help on the Mnesia data layer, which ignores upsert conditions in affected versions.

Configurations

Reachable when a resource uses attribute multitenancy and exposes to callers of one tenant a create action with upsert? true that either upserts on the primary key (no upsert_identity) and accepts it, or upserts on an all_tenants? identity, and the caller knows or can enumerate a key belonging to another tenant (for example a serial integer id, or an id from a shared link or export).

Severity

  • CVSS Score: 7.6 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV.


Release Notes

ash-project/ash (ash)

v3.37.2

Compare Source

Bug Fixes:

v3.37.1

Compare Source

Improvements:
Bug Fixes:
  • wait for an ETS table manager to exit when stopping its table by @​zachdaniel

  • let a contended Mnesia transaction wait instead of failing (#​3084) by Aaron Paterson (#​3084)

  • wait for an ETS table's manager to create the table (#​3083) by Aaron Paterson (#​3083)

  • return the results of a Mnesia aggregate query (#​3085) by Aaron Paterson (#​3085)

  • load before destroying records in streaming bulk destroys by @​zachdaniel

  • don't require original data for atomic bulk actions that won't notify by @​zachdaniel

  • apply an upsert_condition passed to Ash.create by @​zachdaniel

  • keep an aggregate query's arguments when authorizing its relationship path by @​zachdaniel

  • try every operator signature before reporting a cast error by @​zachdaniel

  • don't store :ok as a notification when a managed belongs_to fails in bulk actions by @​zachdaniel

  • return errors from cascade_destroy and after_batch hooks instead of raising by @​zachdaniel

  • apply the smaller of a relationship's limit and its query's limit by @​zachdaniel

  • honor requested strategies when bulk update authorization needs initial data by @​zachdaniel

  • [security] always lateral join through relationships (CVE-2026-114214, GHSA-g2h4-xp57-q863) by @​zachdaniel

  • do not choose atomic_batches strategy incorrectly by @​zachdaniel

  • honor skip_unknown_inputs constraint on embeddable types by @​zachdaniel

  • handle expression calculations in simulating calculation loading by @​zachdaniel

  • make the lack of support for path option explicit in Ash.aggregate by @​zachdaniel

  • include expr & expr_type in unique name for inline aggregates by @​zachdaniel

  • always select temporal period as its needed for loading by @​zachdaniel

  • ensure that changeset.tenant is set on upgraded changesets by @​zachdaniel

  • don't raise on a non-bang get_by call by @​zachdaniel

  • ensure multiple unrelated aggregate authorizations don't conflate by @​zachdaniel

  • ensure aggregate multitenancy is passed everywhere by @​zachdaniel

  • apply operator overloads more strictly only on known matches by @​zachdaniel

  • ensure that upsert_conflict/1 expression is properly typed by @​zachdaniel

  • ensure stream bulk actions apply changeset filter by @​zachdaniel

  • ensure atomic upgrade uses same transaction semantics as normal update by @​zachdaniel

  • read each step of a through relationship the way its relationship reads by @​zachdaniel

  • handle sigils in expressions more gracefully by @​zachdaniel

v3.37.0

Compare Source

Features:
Improvements:
Bug Fixes:
  • discard queued notifications when a transaction ends in a throw or exit (#​3054) by @​Torkan (#​3054)

  • don't produce "not in allowed" error for nil enum value in atomics by @​zachdaniel

  • get relationship paths from custom expressions by @​zachdaniel

  • honor as_of range in temporal bulk updates and destroys (#​3051) by @​yosalama (#​3051)

  • keep each version's values when loading onto temporal records (#​3052) by @​yosalama (#​3052)

  • ensure that authorize? option doesn't conflict on calc dep loads by @​zachdaniel

  • ensure reread uses as_of instead of producing stale error (#​3048) by @​manuganji (#​3048)

  • preserve compiler environment for namespaced interfaces (#​3047) by jeffhuen (#​3047)

  • don't reuse the stored timestamp for a record for destroying by @​zachdaniel

  • enable composite types to act as maps in queries and calculations (#​3045) by Nöl (#​3045)

  • allow present at_least/at_most validations on atomic updates (#​3044) by BBopsCode (#​3044)

  • don't use read action to find parent() referenced rows in ets by @​zachdaniel

  • select "selected by default" attributes for bulk destroy by @​zachdaniel

  • declare boolean return types for contains/2 (#​3042) by leonqadirie (#​3042)

  • retry failed NewType array item casts as nil for empty strings by leonqadirie (#​3042)

  • keep tuple field positions when loading stored values by leonqadirie (#​3042)

  • return an error when loading undeclared composite fields by leonqadirie (#​3042)

  • leave composite values unchanged when they lack a loaded field by leonqadirie (#​3042)

  • reject duplicate and non-list fields in composite type init by leonqadirie (#​3042)

  • check tuple size and report every invalid field in tuple constraints by leonqadirie (#​3042)

  • collect exception errors from every invalid struct field by leonqadirie (#​3042)

  • name the failing field in Map, Keyword and Tuple cast errors by leonqadirie (#​3042)

  • format composite constraint errors like cast errors by leonqadirie (#​3042)

  • include return_query? tuples and error returns in read, page and apply_to specs (#​3041) by Łukasz Samson (#​3041)

  • correct specs for page_opts, load, refute_has_error and Policy.solve (#​3040) by Łukasz Samson (#​3040)

  • various issues with sort + aggregate type determination by @​zachdaniel

  • preserve related records when loading forbidden relationships (#​3039) by MiGoYAm (#​3039)

  • move elixir version requirement to 1.17 by @​zachdaniel

  • drain pending calculations before returning an error (#​3035) by Jake Schurch (#​3035)

  • validate calculation arguments once and preserve input errors (#​3031) by Barnabas Jovanovics (#​3031)

  • properly set tenant on all action results by @​zachdaniel

  • fail atomic changes with their errors instead of crashing (#​3033) by @​Torkan (#​3033)

Performance Improvements:

Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ash](https://hex.pm/packages/ash) ([source](https://github.com/ash-project/ash)) | prod | minor | `3.36.1` → `3.37.2` | --- ### Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records [CVE-2026-114214](https://nvd.nist.gov/vuln/detail/CVE-2026-114214) / EEF-CVE-2026-114214 / [GHSA-g2h4-xp57-q863](https://github.com/advisories/GHSA-g2h4-xp57-q863) <details> <summary>More information</summary> #### Details ##### Summary Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a `through` relationship. When a `has_many` relationship declared with `through:` was loaded for a single record with a limit of 1, or an unsorted `has_one` `through` relationship was loaded with a limit of 1, `lateral_join?/4` in `lib/ash/actions/read/relationships.ex` chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an `offset`. The read still runs the destination's policies but carries the relationship as `accessing_from`, so a client paging such a field (for example `teachers(limit: 1, offset: n)` through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship. This issue affects ash: from 3.24.0 before 3.37.1. ##### Impact A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship. ##### Configurations Reachable when a `through` relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource's read policies rely on the relationship (`accessing_from`) or are otherwise open to the caller. #### Severity - CVSS Score: 6.0 / 10 (Medium) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N` #### References - [https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863](https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863) - [https://cna.erlef.org/cves/CVE-2026-114214.html](https://cna.erlef.org/cves/CVE-2026-114214.html) - [https://github.com/ash-project/ash/commit/24f41e23dcbd9d07cde270a8141490e8f79251f5](https://github.com/ash-project/ash/commit/24f41e23dcbd9d07cde270a8141490e8f79251f5) - [https://github.com/ash-project/ash/commit/e37463307304b26bc8fd606322e5c4d8f7f060e5](https://github.com/ash-project/ash/commit/e37463307304b26bc8fd606322e5c4d8f7f060e5) - [https://hex.pm/packages/ash](https://hex.pm/packages/ash) This data is provided by [OSV](https://osv.dev/vulnerability/EEF-CVE-2026-114214). </details> --- ### An upsert on the primary key in Ash ignores attribute multitenancy, so one tenant can read, overwrite and take over another tenant's records [CVE-2026-96581](https://nvd.nist.gov/vuln/detail/CVE-2026-96581) / EEF-CVE-2026-96581 / [GHSA-vw7c-67pf-gh96](https://github.com/advisories/GHSA-vw7c-67pf-gh96) <details> <summary>More information</summary> #### Details ##### Summary Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take over another tenant's records via an upserting create action. Under attribute multitenancy, `Ash.Actions.Create` (`lib/ash/actions/create/create.ex`) and `Ash.Actions.Create.Bulk` (`lib/ash/actions/create/bulk.ex`) upserted on the primary key, or on an `all_tenants?` identity, without scoping the conflicting record to the request's tenant. A caller of a create action with `upsert? true` that accepts the primary key, supplying a record id from another tenant, updated that record's upsert fields and received all of its attributes in the result. With the default upsert fields the tenant attribute was written too, moving the record into the caller's tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller's own. This issue affects ash: from 1.22.0 before 3.37.2. ##### Impact A signed-in user of one tenant posts another tenant's record id to an upserting create action, receives that record's attributes, overwrites its upsert fields, and with the default upsert fields moves it into their own tenant. ##### Workarounds Add `upsert_condition expr(<tenant attribute> == ^tenant())` to every create action that upserts on the primary key or on an `all_tenants?` identity, and do not combine it with `return_skipped_upsert?`. An upsert into another tenant's record then fails with `Ash.Error.Changes.StaleRecord` (or is skipped in a bulk create) and leaves that record unchanged. This does not help on the Mnesia data layer, which ignores upsert conditions in affected versions. ##### Configurations Reachable when a resource uses attribute multitenancy and exposes to callers of one tenant a create action with `upsert? true` that either upserts on the primary key (no `upsert_identity`) and accepts it, or upserts on an `all_tenants?` identity, and the caller knows or can enumerate a key belonging to another tenant (for example a serial integer id, or an id from a shared link or export). #### Severity - CVSS Score: 7.6 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N` #### References - [https://github.com/ash-project/ash/security/advisories/GHSA-vw7c-67pf-gh96](https://github.com/ash-project/ash/security/advisories/GHSA-vw7c-67pf-gh96) - [https://cna.erlef.org/cves/CVE-2026-96581.html](https://cna.erlef.org/cves/CVE-2026-96581.html) - [https://github.com/ash-project/ash/commit/2333d01ddf37e5909769a513059b27e3183331c5](https://github.com/ash-project/ash/commit/2333d01ddf37e5909769a513059b27e3183331c5) - [https://github.com/ash-project/ash/commit/c9f0cdb31e7c084def05f3f5be69dd7bb7721754](https://github.com/ash-project/ash/commit/c9f0cdb31e7c084def05f3f5be69dd7bb7721754) - [https://hex.pm/packages/ash](https://hex.pm/packages/ash) This data is provided by [OSV](https://osv.dev/vulnerability/EEF-CVE-2026-96581). </details> --- ### Release Notes <details> <summary>ash-project/ash (ash)</summary> ### [`v3.37.2`](https://github.com/ash-project/ash/blob/HEAD/CHANGELOG.md#v3372-2026-10-26) [Compare Source](https://github.com/ash-project/ash/compare/v3.37.1...v3.37.2) ##### Bug Fixes: - don't crash a bulk create when an upsert it runs singly is skipped by [@&#8203;zachdaniel](https://github.com/zachdaniel) - \[security] scope upserts to the tenant under attribute multitenancy ([CVE-2026-96581](https://cna.erlef.org/cves/CVE-2026-96581.html), [GHSA-vw7c-67pf-gh96](https://github.com/ash-project/ash/security/advisories/GHSA-vw7c-67pf-gh96)) by [@&#8203;zachdaniel](https://github.com/zachdaniel) ### [`v3.37.1`](https://github.com/ash-project/ash/blob/HEAD/CHANGELOG.md#v3371-2026-10-25) [Compare Source](https://github.com/ash-project/ash/compare/v3.37.0...v3.37.1) ##### Improvements: - support maps as tuple inputs by [@&#8203;zachdaniel](https://github.com/zachdaniel) - add `Ash.unpaginated_read` by [@&#8203;zachdaniel](https://github.com/zachdaniel) - support `strict?: true` on changesets for strict loading by [@&#8203;zachdaniel](https://github.com/zachdaniel) ##### Bug Fixes: - wait for an ETS table manager to exit when stopping its table by [@&#8203;zachdaniel](https://github.com/zachdaniel) - let a contended Mnesia transaction wait instead of failing ([#&#8203;3084](https://github.com/ash-project/ash/issues/3084)) by Aaron Paterson [(#&#8203;3084)](https://github.com/ash-project/ash/pull/3084) - wait for an ETS table's manager to create the table ([#&#8203;3083](https://github.com/ash-project/ash/issues/3083)) by Aaron Paterson [(#&#8203;3083)](https://github.com/ash-project/ash/pull/3083) - return the results of a Mnesia aggregate query ([#&#8203;3085](https://github.com/ash-project/ash/issues/3085)) by Aaron Paterson [(#&#8203;3085)](https://github.com/ash-project/ash/pull/3085) - load before destroying records in streaming bulk destroys by [@&#8203;zachdaniel](https://github.com/zachdaniel) - don't require original data for atomic bulk actions that won't notify by [@&#8203;zachdaniel](https://github.com/zachdaniel) - apply an upsert\_condition passed to Ash.create by [@&#8203;zachdaniel](https://github.com/zachdaniel) - keep an aggregate query's arguments when authorizing its relationship path by [@&#8203;zachdaniel](https://github.com/zachdaniel) - try every operator signature before reporting a cast error by [@&#8203;zachdaniel](https://github.com/zachdaniel) - don't store :ok as a notification when a managed belongs\_to fails in bulk actions by [@&#8203;zachdaniel](https://github.com/zachdaniel) - return errors from cascade\_destroy and after\_batch hooks instead of raising by [@&#8203;zachdaniel](https://github.com/zachdaniel) - apply the smaller of a relationship's limit and its query's limit by [@&#8203;zachdaniel](https://github.com/zachdaniel) - honor requested strategies when bulk update authorization needs initial data by [@&#8203;zachdaniel](https://github.com/zachdaniel) - \[security] always lateral join through relationships ([CVE-2026-114214](https://cna.erlef.org/cves/CVE-2026-114214.html), [GHSA-g2h4-xp57-q863](https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863)) by [@&#8203;zachdaniel](https://github.com/zachdaniel) - do not choose `atomic_batches` strategy incorrectly by [@&#8203;zachdaniel](https://github.com/zachdaniel) - honor `skip_unknown_inputs` constraint on embeddable types by [@&#8203;zachdaniel](https://github.com/zachdaniel) - handle expression calculations in simulating calculation loading by [@&#8203;zachdaniel](https://github.com/zachdaniel) - make the lack of support for `path` option explicit in `Ash.aggregate` by [@&#8203;zachdaniel](https://github.com/zachdaniel) - include expr & expr\_type in unique name for inline aggregates by [@&#8203;zachdaniel](https://github.com/zachdaniel) - always select temporal period as its needed for loading by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure that changeset.tenant is set on upgraded changesets by [@&#8203;zachdaniel](https://github.com/zachdaniel) - don't raise on a non-bang `get_by` call by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure multiple unrelated aggregate authorizations don't conflate by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure aggregate multitenancy is passed everywhere by [@&#8203;zachdaniel](https://github.com/zachdaniel) - apply operator overloads more strictly only on known matches by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure that upsert\_conflict/1 expression is properly typed by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure stream bulk actions apply changeset filter by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure atomic upgrade uses same transaction semantics as normal update by [@&#8203;zachdaniel](https://github.com/zachdaniel) - read each step of a through relationship the way its relationship reads by [@&#8203;zachdaniel](https://github.com/zachdaniel) - handle sigils in expressions more gracefully by [@&#8203;zachdaniel](https://github.com/zachdaniel) ### [`v3.37.0`](https://github.com/ash-project/ash/blob/HEAD/CHANGELOG.md#v3370-2026-10-22) [Compare Source](https://github.com/ash-project/ash/compare/v3.36.1...v3.37.0) ##### Features: - allow annotating calculations as `authorize? true` by [@&#8203;zachdaniel](https://github.com/zachdaniel) ##### Improvements: - sign keyset pagination cursors ([#&#8203;3038](https://github.com/ash-project/ash/issues/3038)) by Ahatch3 [(#&#8203;3038)](https://github.com/ash-project/ash/pull/3038) - document loading the same relationship and its effects ([#&#8203;3034](https://github.com/ash-project/ash/issues/3034)) by Mckay Hinds [(#&#8203;3034)](https://github.com/ash-project/ash/pull/3034) ##### Bug Fixes: - discard queued notifications when a transaction ends in a throw or exit ([#&#8203;3054](https://github.com/ash-project/ash/issues/3054)) by [@&#8203;Torkan](https://github.com/Torkan) [(#&#8203;3054)](https://github.com/ash-project/ash/pull/3054) - don't produce "not in allowed" error for `nil` enum value in atomics by [@&#8203;zachdaniel](https://github.com/zachdaniel) - get relationship paths from custom expressions by [@&#8203;zachdaniel](https://github.com/zachdaniel) - honor `as_of` range in temporal bulk updates and destroys ([#&#8203;3051](https://github.com/ash-project/ash/issues/3051)) by [@&#8203;yosalama](https://github.com/yosalama) [(#&#8203;3051)](https://github.com/ash-project/ash/pull/3051) - keep each version's values when loading onto temporal records ([#&#8203;3052](https://github.com/ash-project/ash/issues/3052)) by [@&#8203;yosalama](https://github.com/yosalama) [(#&#8203;3052)](https://github.com/ash-project/ash/pull/3052) - ensure that `authorize?` option doesn't conflict on calc dep loads by [@&#8203;zachdaniel](https://github.com/zachdaniel) - ensure reread uses `as_of` instead of producing stale error ([#&#8203;3048](https://github.com/ash-project/ash/issues/3048)) by [@&#8203;manuganji](https://github.com/manuganji) [(#&#8203;3048)](https://github.com/ash-project/ash/pull/3048) - preserve compiler environment for namespaced interfaces ([#&#8203;3047](https://github.com/ash-project/ash/issues/3047)) by jeffhuen [(#&#8203;3047)](https://github.com/ash-project/ash/pull/3047) - don't reuse the stored timestamp for a record for destroying by [@&#8203;zachdaniel](https://github.com/zachdaniel) - enable composite types to act as maps in queries and calculations ([#&#8203;3045](https://github.com/ash-project/ash/issues/3045)) by Nöl [(#&#8203;3045)](https://github.com/ash-project/ash/pull/3045) - allow present at\_least/at\_most validations on atomic updates ([#&#8203;3044](https://github.com/ash-project/ash/issues/3044)) by BBopsCode [(#&#8203;3044)](https://github.com/ash-project/ash/pull/3044) - don't use read action to find parent() referenced rows in ets by [@&#8203;zachdaniel](https://github.com/zachdaniel) - select "selected by default" attributes for bulk destroy by [@&#8203;zachdaniel](https://github.com/zachdaniel) - declare boolean return types for contains/2 ([#&#8203;3042](https://github.com/ash-project/ash/issues/3042)) by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - retry failed NewType array item casts as nil for empty strings by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - keep tuple field positions when loading stored values by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - return an error when loading undeclared composite fields by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - leave composite values unchanged when they lack a loaded field by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - reject duplicate and non-list fields in composite type init by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - check tuple size and report every invalid field in tuple constraints by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - collect exception errors from every invalid struct field by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - name the failing field in Map, Keyword and Tuple cast errors by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - format composite constraint errors like cast errors by leonqadirie [(#&#8203;3042)](https://github.com/ash-project/ash/pull/3042) - include return\_query? tuples and error returns in read, page and apply\_to specs ([#&#8203;3041](https://github.com/ash-project/ash/issues/3041)) by Łukasz Samson [(#&#8203;3041)](https://github.com/ash-project/ash/pull/3041) - correct specs for page\_opts, load, refute\_has\_error and Policy.solve ([#&#8203;3040](https://github.com/ash-project/ash/issues/3040)) by Łukasz Samson [(#&#8203;3040)](https://github.com/ash-project/ash/pull/3040) - various issues with sort + aggregate type determination by [@&#8203;zachdaniel](https://github.com/zachdaniel) - preserve related records when loading forbidden relationships ([#&#8203;3039](https://github.com/ash-project/ash/issues/3039)) by MiGoYAm [(#&#8203;3039)](https://github.com/ash-project/ash/pull/3039) - move elixir version requirement to 1.17 by [@&#8203;zachdaniel](https://github.com/zachdaniel) - drain pending calculations before returning an error ([#&#8203;3035](https://github.com/ash-project/ash/issues/3035)) by Jake Schurch [(#&#8203;3035)](https://github.com/ash-project/ash/pull/3035) - validate calculation arguments once and preserve input errors ([#&#8203;3031](https://github.com/ash-project/ash/issues/3031)) by Barnabas Jovanovics [(#&#8203;3031)](https://github.com/ash-project/ash/pull/3031) - properly set tenant on all action results by [@&#8203;zachdaniel](https://github.com/zachdaniel) - fail atomic changes with their errors instead of crashing ([#&#8203;3033](https://github.com/ash-project/ash/issues/3033)) by [@&#8203;Torkan](https://github.com/Torkan) [(#&#8203;3033)](https://github.com/ash-project/ash/pull/3033) ##### Performance Improvements: - further optimize expression caching by [@&#8203;zachdaniel](https://github.com/zachdaniel) - policy: specialize fallback expressions for known actions ([#&#8203;3036](https://github.com/ash-project/ash/issues/3036)) by Jake Schurch [(#&#8203;3036)](https://github.com/ash-project/ash/pull/3036) </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNjUuMiIsInVwZGF0ZWRJblZlciI6IjQzLjE2NS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0ZWQiLCJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSIsInNlY3VyaXR5Il19-->
chore(deps): update dependency ash to v3.37.2 [security]
All checks were successful
continuous-integration/drone/push Build is passing
8506e45476
simon closed this pull request 2026-11-04 12:28:59 +01:00
Some checks are pending
continuous-integration/drone/push Build is passing
continuous-integration/drone/pr
Required

Pull request closed

Sign in to join this conversation.
No description provided.