Android / Build, or is the channel already serving this? (push) Successful in 4s
CI & Build / Build now, or wait for Android? (push) Successful in 4s
CI & Build / Python lint (push) Successful in 2s
CI & Build / TypeScript typecheck (push) Successful in 11s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 3s
CI & Build / Python tests (push) Successful in 15s
CI & Build / integration (push) Successful in 58s
CI & Build / Build & push image (push) Skipped
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 4m17s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 7m50s
Desktop (Tauri) / Update manifest (push) Successful in 5s
Android / Kotlin + Rust (APK) (push) Successful in 11m37s
ThoughtSync is renamed Inkwell ("Fabled Inkwell" in full; Scribe note 5071).
This is step 1 of milestone 481: every string a person reads in the running
apps. Identities installed clients depend on are deliberately untouched — the
Tauri productName (it derives the .deb Package: field), identifier and binary
name, applicationId, X-ThoughtSync-* headers, the export's app marker, env vars,
module and crate names.
- web: title, PWA manifest (name "Fabled Inkwell", short_name "Inkwell"),
offline page, icon labels, build labels, prompts, notification title
- server: site_name default, import error, link-preview User-Agent
- 0030: a stored site_name of exactly the old default follows the rename. The
Settings page saves every key, so most servers hold "ThoughtSync" without an
admin ever having chosen it; a name they typed is left alone
- desktop: window title, default device name, local-mode site name, log line
- android: app_name and the strings that name the app
- core: probe and compatibility messages
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
52 lines
1.6 KiB
Python
52 lines
1.6 KiB
Python
"""a stored site_name of the old default follows the rename to Inkwell
|
|
|
|
Revision ID: 0030
|
|
Revises: 0029
|
|
Create Date: 2026-10-06
|
|
|
|
The product is renamed ThoughtSync → Inkwell (Scribe note 5071), and the `site_name`
|
|
registry default moves with it. On its own that only reaches servers whose settings
|
|
table has no `site_name` row — and most servers have one, because the Settings page
|
|
saves EVERY key on Save, not just the one that changed. An admin who opened Settings
|
|
to flip registration off has persisted `"ThoughtSync"` without ever choosing it.
|
|
|
|
So the row is rewritten, but only when it holds exactly the old default. A name the
|
|
admin actually typed is theirs and is left alone; the old default is the one value we
|
|
can be sure nobody chose.
|
|
|
|
The match is on the stored JSON text (`settings.value` is `json.dumps(value)`), so
|
|
`'"ThoughtSync"'` is the whole of what it looks for.
|
|
|
|
## Downgrade
|
|
|
|
Puts the old default back on a row holding exactly the new one. A server where the
|
|
admin typed "Inkwell" themselves between the two cannot be told apart from one this
|
|
migration rewrote; on downgrade both read "ThoughtSync", which is what the old code
|
|
would have shown for either.
|
|
"""
|
|
from alembic import op
|
|
import sqlalchemy as sa
|
|
|
|
revision = "0030"
|
|
down_revision = "0029"
|
|
branch_labels = None
|
|
depends_on = None
|
|
|
|
_OLD = '"ThoughtSync"'
|
|
_NEW = '"Inkwell"'
|
|
|
|
|
|
def _swap(old: str, new: str) -> None:
|
|
op.get_bind().execute(
|
|
sa.text("UPDATE settings SET value = :new WHERE key = 'site_name' AND value = :old"),
|
|
{"old": old, "new": new},
|
|
)
|
|
|
|
|
|
def upgrade() -> None:
|
|
_swap(_OLD, _NEW)
|
|
|
|
|
|
def downgrade() -> None:
|
|
_swap(_NEW, _OLD)
|