Decision: pin AshAuthentication 4.15 rather than the 5.0 release candidate #7

New issue

Open

opened 2026-09-26 13:58:29 +00:00 by belvedere · 0 comments

belvedere commented

2026-09-26 13:58:29 +00:00

Collaborator

Objective: Record the auth library choice so it is not silently churned later.

As of 2026-09-26 on hex.pm: ash_authentication latest stable is 4.15.0, with a 5.0.0-rc.*
series in progress; ash_authentication_phoenix stable is 2.17.4 (3.0.0-rc.* in progress).

Decision: use the stable pair (~> 4.15 / ~> 2.17) for v1.

Rationale: an RC auth stack carries upgrade churn and breaking API risk for a project whose
risky part is the SRS engine and the data pipeline, not authentication. Revisit after 5.0 ships.

Files:

Create: docs/decisions/0001-ash-authentication-version.md

Verify: the doc states the versions, the date checked, and the revisit trigger
("revisit when ash_authentication 5.0.0 final is released").

**Objective:** Record the auth library choice so it is not silently churned later. As of 2026-09-26 on hex.pm: `ash_authentication` latest **stable** is `4.15.0`, with a `5.0.0-rc.*` series in progress; `ash_authentication_phoenix` stable is `2.17.4` (3.0.0-rc.* in progress). **Decision:** use the stable pair (`~> 4.15` / `~> 2.17`) for v1. **Rationale:** an RC auth stack carries upgrade churn and breaking API risk for a project whose risky part is the SRS engine and the data pipeline, not authentication. Revisit after 5.0 ships. **Files:** - Create: `docs/decisions/0001-ash-authentication-version.md` **Verify:** the doc states the versions, the date checked, and the revisit trigger ("revisit when ash_authentication 5.0.0 final is released").

belvedere added this to the M1 — Ash foundations, auth & app shell milestone

2026-09-26 13:58:29 +00:00

belvedere added the

labels

2026-09-26 13:58:29 +00:00

belvedere referenced this issue

2026-09-26 14:01:56 +00:00

Decision: pin AshAuthentication 4.15 rather than the 5.0 release candidate #59