Skip to content

Promote dev → main (5 commits) - #1228

Open
github-actions[bot] wants to merge 13 commits into
mainfrom
dev
Open

github-actions[bot] wants to merge 13 commits into
mainfrom
dev

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Automated promotion: dev reached 5 commits ahead of main with green CI (server + webapp). Review and merge to cut a release.

claude and others added 13 commits October 6, 2026 14:48
Re-lock fid at the Ed25519 release, which no longer depends on @akaoio/zen,
and make the test double mirror the real sign/verify.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
The previous lockfile was generated with --legacy-peer-deps and lost the
optional peers (search-insights, @types/react) that npm ci expects.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
chore(fid): move to fid 5.0.0 (Ed25519, no Zen SEA)
…rom docs

Adds GET/PUT /api/auth/zen/library/:pub and a public shared-playlist read,
signed with the FID identity key and limited to active accounts. Replaces
the Zen relay the player used. Updates EN/IT docs to Ed25519 identities and
removes the dead zen type stubs from the webapp.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
feat(auth): library sync over HTTP for the website player; docs without Zen
GET /api/auth/zen/library/:pub/account answers { username } for an active
account linked to the key, 404 otherwise. Replaces the passport sync the
relay used to provide for bootstrapping a second device.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
…ore fid 5

fid 5.0 re-keyed every identity. An account created through FID has no
password (the server refuses to write one), so its owner could not get back
in and the error sent them to a Settings screen that does not exist.
npm run fid:relink lets the operator point the account at the new key; the
SSO and challenge errors now say what happened and who can fix it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
… into claude/dazzling-franklin-yj0co6

# Conflicts:
#	CHANGELOG.md
feat(auth): fid:relink tool + account lookup missing from #1227
A FID-only account whose key changed with fid 5.0 can no longer prove it owns
the account, so signing in through the portal with the new key now records a
relink request (first request wins) that the primary admin approves or
dismisses from the users list. The move logic is shared with fid:relink.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
feat(auth): approve a FID relink from Admin > Users
A signed-in user can mint a single-use link code (5 min) and bind a new FID
key through the portal, without administrator approval.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe
feat(auth): self-service FID relink from the Profile page

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants