- The composer lays out attachments like the saved memo: pictures and
videos in one gallery, audio and files as rows, then links and place,
with no section headers. Editing a memo in place keeps that shape.
- Attachments can be reordered by dragging (long press on touch, the grip
on rows) or with Alt+arrow keys. The dragged item lifts, the others
slide aside around a placeholder, and Escape cancels.
- Saved attachments and new files share one order in the draft
(attachmentOrder), kept through upload retries and applied on save.
An edited drawing keeps the place of the drawing it replaces.
- Link rows show the linked memo's text and date; back-links show
read-only while editing.
- Drawings in a collage get the photos' hairline frame.
- Composer polish: Markdown label beside the commit button, quieter
suggestion pills, a compact recorder row, and kit buttons for upload
anchors.
- Language and theme move from a footer under the card into the card's
bottom row: a ghost language picker and a System/Light/Dark/Paper
segmented control, lined up with the content edges.
- Drop the Explore link, the welcome subtitle, the first-run chip and note,
and the administrator tip.
- /auth/signup sends visitors to sign-in when registration is closed (with a
one-line notice) or when accounts only come from identity providers.
- Wrong credentials and other sign-in or sign-up failures show inside the
form instead of a toast; the password field gets a show/hide button.
- The SSO callback uses the same layout for its wait and its error.
- On phones the card frame drops and the language and theme row sits at the
bottom of the screen.
The v0.31 loader read every memos-idp-*.json, warning only when the name was
not lowercase kebab case, so the startup warning now matches identity provider
files by that prefix and suffix. Instance setting files keep the kebab-case
pattern the loader required.
files
26.10.0 stopped reading the v0.31 deployment configuration files
(memos-idp-*.json, memos-instance-setting-*.json) without a migration,
so an
instance that kept them through the upgrade gave no sign of it beyond
the
settings that had silently reverted. Startup now logs one warning naming
any
such files still present under /etc/secrets, without reading them, and
points
at the configuration directory.
Keeps the caret after a word composed as a block's whole text on
Safari and iOS, where the committed word was selected and the next
keystroke replaced it (#6517).
WriteError now logs the cause of a server error, which the public JSON
body never carries, unless the client has already gone away. The header
reset and envelope move into a shared writer the panic recoverer uses
too, so one failure logs once. The doc comment states the header contract.
A local attachment whose file is gone from disk answers a JSON 404 like
every other storage failure instead of net/http's plain-text page.
The export handler no longer strips the archive headers itself and logs
only the committed case the wrapper cannot see. The fake S3 and local
storage test setups are shared helpers, and the 416 test pins that
Content-Range survives the header reset.
The full-screen preview inherited the dialog primitive's rounded corners,
which overflow-hidden clipped so the page showed through at the top.
Arrow keys stopped switching items because Base UI's dialog popup halts
propagation of composite keys and the dialog traps focus, so the
document-level listener never received them. Listen on the popup itself
and exercise that path in the test instead of firing on document.
The reaction upsert binding renamed its memo field from name to parent,
but the body override still stripped name, so the tool exposed a
redundant parent string beside the path argument. Omit parent instead,
and fail at startup when an override omits a property the request body
no longer has, so a binding rename cannot leave a path-bound field
exposed again.
The evals README authenticated with the demo access token the seed no
longer ships. Declare steven in a configuration directory, which the
demo seed attaches its content to, then sign in and mint a personal
access token for the harness.
A new account's own Home opens a four-page welcome guide once: an intro
with a memo card specimen, then Write, Keep and Share, each headed by a
still life of a real component over icon-and-line rows. It opens while
the
account has no memos and is younger than a week, and a dismissal is kept
in
local storage per account, so nothing is stored on the server. The About
page reopens it.
The timeline's empty states no longer reuse the no-results illustration:
first use shows "No memos yet" with a link to the guide, and a filter
that
finds nothing shows "No matching memos" with a Clear filters action.
The dialog kit gains a borderless "guide" chrome variant; strings ship
in
all locales.
Startup is now migrate, apply the configuration, then seed in demo mode,
the order in which comparable systems bootstrap identity before content.
Seed leaves store.Migrate and becomes a method the server calls after
applyConfigurationAtStartup.
The seed holds content only. The public demo access token and the
MEMO_RELATED row are gone; the reaction list belongs to the configuration.
Users are inserted without fixed ids and only when missing, their profile
fields are filled only where empty, and every memo, membership, reaction,
and attachment references its creator by username. A declared
administrator therefore keeps its row, credentials, and display name, and
the seeded content attaches to it. A bare --demo start without a
configuration seeds the same four users as before.
The seed test covers both starts and asserts the seed writes no instance
or user settings. Two stale lines of copy are fixed.
A configuration file may now declare which identity-provider subject signs
in as a declared user, as a fourth resource kind:
"linkedIdentities": [
{ "name": "users/admin/linkedIdentities/sso", "externalUid": "subject" }
]
An administrator on an SSO-only instance otherwise has no way in before the
first sign-in, which provisions a new account because the sign-in path
matches a provider and subject and nothing else. Matching an email or
username claim was rejected: neither proves ownership on this instance. A
declared subject trusts no claim, and the sign-in path is unchanged.
Rules: the user must be declared in the same configuration, a subject is
declared once, the provider must exist after apply, and a subject already
linked to a different user fails the plan rather than being taken over. A
link made by signing in with the declared subject is adopted; a different
stored subject is replaced. Links are written after users in the apply
transaction. A declared user with a declared link may be created without a
password; it gets an unusable random one, as SSO provisioning does.
The API refuses to create or delete a managed link, and to delete a
provider a declared link names. The account page hides Unlink for a
declared link. LinkedIdentity.external_uid is no longer output only.
Add .github/actions/setup-go (Go version from go.mod) and
.github/actions/setup-web (pnpm from web/package.json, Node 24,
frozen install), and use them in every workflow that installed the
toolchains by hand. Drop the per-workflow version env vars and the
redundant pnpm store cache steps that duplicated setup-node's cache.
The entry for the removed MemoRelatedSetting.enable_double_click_edit
field was added inside the fenced format example at the top of the file,
and the usage limits entry still described the field as present. Move the
entry into the real Unreleased section and state the remaining field.
- Bump @usememos/editor to 26.10.27: Markdown mode now highlights syntax
inside table cells, so a URL anchor in a table-cell link, such as
[Kappa](/memos/abc#ikebukuro), reads as part of the URL instead of a
tag.
Refs usememos/memos#6480 (item 13).
- Focus mode: a narrower sheet (max-w-3xl) with larger text through
MEMO_FOCUS_EDITOR_THEME; its header shows only the memo's time ("Now"
before it has one) and the exit button; toggling it runs a view
transition that grows the frame out of its place on the page and back,
instant under reduced motion or without view transitions.
- Markdown mode's + menu item uses Lucide's CodeXml instead of the
pilcrow.
The frontend handler served index.html for any extensionless path, so
OAuth Protected Resource Metadata probes under /.well-known/ received
HTML with status 200. MCP clients that run RFC 9728 discovery before
trusting the endpoint failed to parse it, while a 404 would have told
them the server does not advertise OAuth.
Paths with a hidden segment are never app routes: usernames, memo UIDs,
and fixed routes all begin with an alphanumeric character. Return 404
for them, following RFC 8615 for /.well-known/ and the dotfile
convention of common static servers for paths like /.git/.
Fixes#6495
The renderer discarded the SQL of an operand that folded to a constant,
such as the left side of `x || true`, but kept the arguments it had already
added. Callers append their own predicates after the filter fragment and
bind positionally, so each leftover argument bound to a later placeholder.
Fold boolean constants out of the condition tree before rendering, so a
subtree either renders with its arguments or not at all, and reject any
rendered fragment whose placeholders and arguments disagree.
Tables are styled like claude.ai's: the table fills the editor's width
with a round frame, a tinted header row, lines between rows and no
vertical lines, and cells wrap at words instead of mid-word. HTML tables
rendered through the html view look the same.
Footnote definitions render their text as Markdown. In read-only memos
the referenced definitions are collected in a section at the end of the
note, above the attachments, in order of first reference, each with a
backlink per reference; unreferenced definitions are left out and
labels show as written. While editing, definitions stay where they are
written.
Both fix items reported in #6480. Wire the editor's two new labels,
`footnotes` and `backToReference`, to new `editor` keys in every locale.
Use neutral, theme-aware surfaces and consistent density for hints,
menus, dialogs, and form controls. Restore visible field focus and use
Base UI tabs for keyboard navigation and RTL support.
Link preview was a Timeline view option, so it reset to on everywhere else.
Double-click to edit was an instance setting an admin chose for everyone.
Both are presentation choices for one browser, so they now live in a single
localStorage-backed store shared by every memo view and are toggled from
Settings > Preferences under "This device".
MemoRelatedSetting.enable_double_click_edit is removed from the API and
storage protos and reactions becomes field 1; stored rows that still carry
the old key load unchanged. The admin Memo page keeps only reactions.