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.
Take the tagline, one-liner, and short description from the rewritten
BRAND.md in usememos/.github and use the serif lockup and the light and
dark timeline previews published there. The README now leads with what a
visitor gets, keeps the quick start to one command plus the URL to open,
drops badges that repeat the sidebar, and carries the star-history
badges
instead of the chart. The local Georgia wordmark is removed.
In the app, the about page, manifest, and English locales carry the same
copy. The identity label uses the theme's serif stack at the wordmark's
weight and spacing rather than a vendored face. The about tagline sizes
to its column so neither sentence breaks mid-line, and the version chip
is the single place for build identity: a release links to its tag and a
development build links to its commit, so the Build commit row and its
locale label are gone.
Share logo and identity typography across navigation, auth, and About
while preserving custom branding.
Use a transparent blue favicon and Celadon installation icons with
refreshed cache versions.
Move memo content size into usage limits, with 8 KiB content and 32 MiB
upload defaults when settings are absent. Represent stored rule targets
with all_users or a positive user_id, and use that same schema for
deployment configuration.
Rename the memo count metric, remove reserved proto declarations, and
renumber fields and enums for the unreleased schema. Synchronize
enforcement, settings UI, generated clients, and tests.
Drop the D1 store driver, its migrations, emulator, design doc, filter
dialect, and test-harness wiring. Memos supports SQLite, MySQL, and
PostgreSQL only.
Exercise real server startup on backend test runs and gate releases on fresh-install, previous-stable upgrade, and entrypoint smoke checks across supported databases.
The canary workflow passed VERSION=canary as a build-arg, so the demo
instance reported "canary" as its version. Derive the version from the
latest git tag instead (e.g. 0.29.1) so the app reports a real semver.
The `canary` image tag is unchanged.
Add area dropdowns, reproduction requirements, regression info, and
compatibility sections to reduce back-and-forth on bug reports and
feature requests.
Replace `labels: [bug]` and `labels: [enhancement]` with `type: Bug`
and `type: Feature` to leverage GitHub's native issue types already
configured on this repo.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add PR stale/close handling alongside issues
- Reduce close grace period from 7 to 3 days
- Add inline comments explaining the two-phase stale behavior
- Rename workflow and job names for clarity
- Add workflow_dispatch trigger for manual binary builds
- Build for linux (amd64, arm64, arm/v7), darwin (amd64, arm64), windows (amd64)
- Package as tar.gz (Unix) and zip (Windows)
- Generate build summary with artifact sizes
Problem:
- store/test/TestMain checks if DRIVER env var is set
- If not set, it runs tests for all 3 drivers (sqlite, mysql, postgres)
by spawning child 'go test' processes
- This conflicts with t.Parallel() in individual tests
- CI workflow didn't set DRIVER, triggering multi-driver execution
Solution:
- Set DRIVER=sqlite in GitHub Actions workflow
- TestMain will run tests once with SQLite driver
- Tests run in parallel with t.Parallel() as intended
- Avoids spawning child processes and race conditions
Why SQLite:
- Fastest test execution (no container startup)
- Sufficient for CI validation
- MySQL/Postgres can be tested locally when needed
This fixes the 'table already exists' errors and test flakiness
in CI while maintaining parallel execution benefits.