Decision: pin AshAuthentication 4.15 rather than the 5.0 release candidate #59
Labels
No labels
area
auth
area
data
area
domain
area
infra
area
stats
area
study
area
tooling
area
ui
duplicate
future
kind
bug
kind
chore
kind
decision
kind
docs
kind
feature
kind
spike
kind
test
prio
blocker
risk
high
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nickkeers/first-thousand-words#59
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Objective: Record the auth library choice so it is not silently churned later.
As of 2026-09-26 on hex.pm:
ash_authenticationlatest stable is4.15.0, with a5.0.0-rc.*series in progress;
ash_authentication_phoenixstable is2.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:
docs/decisions/0001-ash-authentication-version.mdVerify: the doc states the versions, the date checked, and the revisit trigger
("revisit when ash_authentication 5.0.0 final is released").
Duplicate of #7 — created by a re-run whose pagination helper only saw the first page of issues. Closing to keep the backlog clean. Repo owner can delete this outright.