inbuxa/ihasmail-inbuxa
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Use the server's renamed registry capability, urn:inbuxa:jmap:registry #14

Merged
jcoffey-dev merged 1 commits from fork/rename-upstream-identifiers into main 2026-09-23 04:25:13 +00:00
Conversation 0 Commits 1 Files Changed 9
+17 -17
jcoffey-dev commented 2026-09-23 04:14:10 +00:00
Owner
Copy Link
Copy Source

inbuxa-server renames the identifiers that carried the upstream name (its
SPEC.md §2.4). Upstream's capability for the registry (x:) objects is now
urn:inbuxa:jmap:registry, beside the fork's own urn:inbuxa:jmap, which is
unchanged. There's no alias, so this lands with the server change and
deploys with it. The mock advertises the new name too. No user-visible
strings change.

Summary

Related issues

Translations

Testing

Screenshots

inbuxa-server renames the identifiers that carried the upstream name (its SPEC.md §2.4). Upstream's capability for the registry (x:) objects is now urn:inbuxa:jmap:registry, beside the fork's own urn:inbuxa:jmap, which is unchanged. There's no alias, so this lands with the server change and deploys with it. The mock advertises the new name too. No user-visible strings change. <!-- Thanks for contributing to ihasmail. CONTRIBUTING.md has the full guide; this is the short version. Delete any section that does not apply. --> ## Summary <!-- What changes, and why. --> ## Related issues <!-- e.g. Closes #123. Leave blank if there are none. --> ## Translations <!-- Nine languages ship alongside English, and a missing key silently renders its English source -- so an untranslated string is invisible until somebody reading that language finds it. Say which this PR is, explicitly: - Adds or alters user-visible strings: how many keys, and the fallback count before and after. - Adds none. "Adds none" is an answer. Saying nothing is not -- it leaves it to be inferred. See CONTRIBUTING.md -> Translations. --> ## Testing <!-- What you ran, and what you saw. `npm run typecheck`, `npm test` and `npm run build` all run in CI, so the useful thing here is what CI cannot do: which flows you exercised by hand, and against what -- a real Stalwart instance, or `npm run dev:mock`. If the change is visible on screen, drive the built app, not just the store. See CONTRIBUTING.md -> Verifying UI work. --> ## Screenshots <!-- For UI changes. Before/after, or a GIF for anything with motion. -->
jcoffey-dev added 1 commit 2026-09-23 04:14:11 +00:00
Use the server's renamed registry capability, urn:inbuxa:jmap:registry
ci / version (pull_request) Skipped
Details
ci / node (pull_request) Successful in 2m47s
Details
ci / publish (pull_request) Skipped
Details
ci / docker-build (pull_request) Successful in 3m55s
Details
f5dd4e5537 
inbuxa-server renames the identifiers that carried the upstream name (its
SPEC.md §2.4). Upstream's capability for the registry (x:) objects is now
urn:inbuxa:jmap:registry, beside the fork's own urn:inbuxa:jmap, which is
unchanged. There's no alias, so this lands with the server change and
deploys with it. The mock advertises the new name too. No user-visible
strings change.
jcoffey-dev merged commit c0c892dd33 into main 2026-09-23 04:25:13 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcoffey-dev (John Coffey)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/ihasmail-inbuxa#14