Tags

v0.4.1

Vector 0.4.1 restores backups into installations whose database Run Edit Run Platform migrated. Such a database records its migrations in Platform's ledger, which Wrangler cannot read; a local restore or backup used to run Wrangler anyway and stopped at "Preparing archive schema" with "table workspace_settings already exists". Vector now leaves that database to Platform's runner, checks that every migration is applied, and restores the listed version's backups and its own with every archived row, cell and file intact, into Platform-migrated and native installations alike. This release uses rer 0.2.77.

Teams, projects and saved views can post new triage items, new issues and status changes to a Slack channel or a Discord webhook, and a team or project can create its own Slack channel. Members can link their Slack account and receive assignments and mentions as Slack direct messages with Assign to me, Change status and Open actions. Messages carry the identifier, title, actor and status change, never descriptions or comments; credentials are sealed and never travel in backups. TanStack Start is patched for GHSA-qx66-fv34-fjm8.

Apply migrations 0073–0074 after unchanged 0001–0072. Back up before upgrading; retain additive schema and delivery ledgers on rollback.

Known limits: roles, private teams, guests and most provider integrations remain incomplete as shown in CONTRACT.md; Slack app installation through its manifest, @vector issue creation and Teams are not available. Linear and Jira importers are documented-format, synthetic-only; there is no Asana importer. Managed mail relay and broad capacity are not claimed. Local setup and development still migrate with Wrangler; a local database carrying Platform's migration ledger is for backup and restore only. For hosted backups use the authenticated Base transfer client described in CHANGELOG.md.

Product screenshot: docs/retained-verification/ui/1440-app.png

v0.4.0

Vector 0.4.0 adds personal time zones and working hours, light/dark/system appearance, automatic issue closing and archiving, project color and emoji, and daily cycle and project reporting. Reopened discussion threads notify participants who still follow the issue, with a dedicated preference. Projects now have ordered milestones with dates, completion and issue progress; changing projects clears incompatible assignments, and deleting a milestone preserves its issues. Existing intake and planning behavior remains available.

Hosted deployment also retires its unused owner session through the native sign-out response. POST /auth/signout now returns HTTP 204 with no JSON body; scripted clients should accept that success response.

A backup from the catalogue’s previous Vector version now restores with its archived records and file bytes intact. This release uses rer 0.2.74 and applies migrations 0065–0072 after unchanged 0001–0064. Back up before upgrading; retain additive schema and history on rollback.

Known limits: role-specific permissions, private teams, guests and provider integrations remain incomplete as shown in CONTRACT.md. Linear and Jira importers are documented-format, synthetic-only; there is no Asana importer. Milestone grouping, calendar feeds, full public milestone API operations and Jira/Linear milestone mapping remain future work. Managed mail relay, broad capacity and unavailable historical daily report facts are not claimed. The deferral return time uses the browser’s time zone. For hosted backups use the authenticated Base transfer client described in CHANGELOG.md.

Product screenshot: docs/retained-verification/ui/1440-app.png

v0.3.0

Vector 0.3.0 is the planning and follow-up release. Issues gain structured descriptions with checklists and a description history, comment threads you can resolve, follower notifications, snoozes and personal reminders, and ten-second Undo. Planning gains ordered sub-issues with automatic parent progress, related issues, issue copies from the menu, the command palette or the API, a shared manual order, per-person workload, project start dates, priorities, labels and a stated reason for project health, and automatic team cycle schedules.

Reports from monitoring or support tools reach Needs decision through a secret webhook URL (with Zapier, Make and UptimeRobot steps) as well as signed senders. Moving in now also accepts Plane CSV, Shortcut CSV and Huly JSON files through the same reviewed, staged import.

Checked before release: an independent gate ran Vector's whole loop locally at 1440 and 390 and on a hosted installation with real email: a source report landed in Needs decision, was deferred and came back on time (and sooner when new evidence arrived), was accepted with a reason and routed into Now; Current, My work, Board, saved views, Inbox, project health, cycle rollover and Command-K search all worked; an invited teammate signed in from the emailed link and received assignment email, and the owner received mention email. A populated v0.2.0 installation upgraded with its data (migrations 0050 to 0064). A hosted backup was taken, the installation removed and redeployed, and the backup restored with all its records and file bytes.

Known issues: restoring a backup into a hosted installation made by rer deploy is refused (restore_bootstrap_not_pristine), so restore locally with rer import; a hosted backup uses Base's transfer client with the owner's session (see CHANGELOG.md), because rer export and wrangler d1 export cannot read the hosted database. The deferral return time is entered in your browser's time zone.

Product screenshot: docs/retained-verification/ui/1440-app.png

Vector v0.2.0

Vector 0.2.0 is a breaking upgrade from 0.1.0: it adopts the public rer lifecycle with canonical local state, and `pnpm run deploy` now means `rer deploy`, while controller-deployed v0.1.0 installations update with `pnpm artifact:deploy` (docs/HOSTED-UPGRADE.md) and local v0.1.0 data moves via docs/LOCAL-RECOVERY.md. Migrations 0012-0049 apply in order after unchanged 0001-0011; 0046 is destructive and deletes pending identity-dependency approvals, which owners must renew. The release adds Settings administration, issue lists, boards, saved views and search; private Inbox, mentions and daily reminders; reviewed CSV/JSON, Linear and Jira imports, portable archives, restore and imported-person erasure; scoped API tokens, signed source ingestion, GitHub PR links and outbound webhooks; native owner claim, `rer signin` and the approved brand. Managed-relay hosted acceptance is blocked by Base patch gr-base-162 and is not proven; Linear/Jira imports remain synthetic-only.

Pins: @runeditrun/rer 0.2.22, Node 22.20.0, pnpm 10.12.4.