| name | timely-release-manager |
| description | Use this whenever the user asks to prepare, verify, or publish a Timely release or prerelease, bump versions, generate GitHub release notes, validate updater channels, update localized in-app What's New notes, or work on release/localization rules. Trigger on release, prerelease, beta, tag, changelog, updater manifest, gh release, publish, cut release, ship build, localization, i18n, release notes, highlights, Spanish, Portuguese, es, pt. |
Timely Release Manager
Orchestrates Timely's release and prerelease workflow: version sync, localized highlights, updater channel validation, quality gates, commit, and GitHub publish.
Reference files
Load these as needed — they contain the detail; this file is the map.
| File | Load when |
|---|
references/workflow.md | Starting any release task — contains the full 9-step procedure |
references/version-files.md | Bumping versions — exact files, fields, and lock-refresh commands |
references/notes-templates.md | Writing GitHub release notes — prerelease and stable templates |
references/highlights-localization.md | Writing or reviewing es/pt copy — always load before editing localized content |
Release invariants
Enforce these on every release, regardless of type:
- Version is synchronized across all 5 files (see
version-files.md).
- Highlights key = bare version string with no
v prefix.
- Highlights include all three locales:
en, es, pt.
- Locale copy is adapted, not literally translated (see
highlights-localization.md).
- Updater channel matches release type: prerelease →
unstable, stable → stable.
- All quality gates pass before commit or publish.
- No internal labels in release notes — Ban "Phase N", "refactor(s)", "readonly", "globalThis", "code-split", "boundary", and similar jargon. Run the failsafe checklist in
notes-templates.md before publish.
- First-class localization — Spanish and Portuguese must have zero English words. Load
highlights-localization.md before editing es/pt copy. See AGENTS.md § Localization.
Input defaults
When the user doesn't specify:
release_type: infer from version suffix (-beta, -rc, no suffix = stable)publish_now: false unless the user explicitly asks to publish- Notes style: match the last two same-type releases (
gh release list --limit 10)
Workflow summary
Read references/workflow.md for the full procedure. The 9 steps at a glance:
- Inspect current state (git + recent releases)
- Validate updater channel and highlights wiring
- Bump version across all 5 files
- Add/update localized in-app highlights
- Update version-sensitive tests
- Run quality gates (fmt / lint / test for JS + Rust)
- Commit with
chore(release): prep v<version>
- Publish via
gh release create (only when explicitly requested)
- Post-publish verification
Localization rules (es/pt)
When editing release highlights, i18n strings, or any user-facing copy in Spanish or Portuguese:
- Load
references/highlights-localization.md — contains banned terms, equivalents, and writing principles.
- Zero English words — scrollbar → barra de desplazamiento/rolagem; setup → configuración/configuração; tray → bandeja del/do sistema; updater → actualizador/atualizador; build/release → versión/versão.
- Adapt, don't translate — each locale reads as native product copy, not English with swapped words.
Key source files
package.json version + prerelease dev scripts
package-lock.json auto-regenerated via npm install --package-lock-only
src-tauri/Cargo.toml Rust package version
src-tauri/Cargo.lock auto-regenerated via cargo check
src-tauri/tauri.conf.json Tauri bundle version
src/core/services/ReleaseHighlights/ in-app What's New content (all locales)
src/core/services/I18nService/i18n.tsx app-wide i18n strings (en, es, pt)
src/core/layout/MainLayout/MainLayout.tsx reads highlights, shows dialog
src-tauri/src/commands/updates.rs updater endpoint constants
src-tauri/src/services/preferences.rs default_update_channel() logic
