citesvue
Changelog

What shipped, when, and why.

A version-by-version record of what changed on Citesvue. Features, improvements, fixes, security updates, and deprecations — each entry tagged so you can scan for the bits relevant to your role. Material changes get linked back to the underlying decision in the post-incident report or design doc where one exists. Breaking API changes always get at least 90 days’ notice; check /roadmap for what’s queued next.

Subscribe (RSS)See the roadmap
TagsNewImprovedFixSecurityBreakingAPI
  1. 2026-04-18
    v0.9.0
    Release

    Region pinning for Enterprise.

    Workspace-level data residency selection (EU-only / US-only) now ships on Enterprise, including for sub-processor invocations where the provider supports regional routing. Audit log surfaces every region decision per recording.

    • NewRegion pinning settings under Workspace → Trust → Residency. Honoured by every component including LLM, ASR, and OCR routes.
    • NewNew audit-log event types: residency.chosen, residency.changed, residency.crossed (only ever fires when an admin opts a workload out of its pin).
    • ImprovedQ&A copilot adds a region-aware router; EU latency on Q&A drops by ~40% under upstream pressure (followed the 12-Apr incident).
    • APINew header on every API response: x-citesvue-region. Distinguishes which region served the request.
    • FixRecording ingestion: assembly worker memory ceiling raised; fixes 2GB+ stalls reported in the 24-day-ago incident.
  2. 2026-04-04
    v0.8.4
    Release

    Frame-level citations.

    Q&A answers can now cite a specific frame (timestamped screenshot) alongside the transcript line. The cited mark renders as a clickable thumbnail with hover-to-zoom.

    • NewFrame citations available in Q&A answers, exports (DOCX, PDF), and the API response.
    • NewVisual intelligence: per-frame OCR exposed on the artifact view; copy-as-text on hover.
    • ImprovedCitation density auto-tunes to question intent — answers no longer cite 14 separate frames when 2 will do.
    • APIGET /v1/answers now returns a citations[] array including {kind:"frame", recording_id, t_ms, image_url} entries.
  3. 2026-03-22
    v0.8.3
    Release

    Jira & Linear push: bidirectional linkback.

    Pushing an artifact to Jira or Linear now creates a back-pointer in Citesvue. Comments on the issue surface inline next to the original recording context.

    • NewBidirectional sync for Jira and Linear: artifact ↔ issue mapping persists; status changes reflect in Citesvue.
    • NewPer-tenant fair-share scheduling for outbound webhooks (followed the 31-day-ago incident).
    • ImprovedSlack digests support per-channel routing rules and quiet hours.
    • FixConfluence push: fixed an edge case where decision artifacts were exported without the linked transcript window.
  4. 2026-03-09
    v0.8.2
    Release

    SSO with SCIM 2.0 in beta.

    SAML 2.0 / OIDC was already there. SCIM 2.0 provisioning lands in beta on Business and Enterprise, with role-mapping presets for Okta, Entra ID, JumpCloud, and Google Workspace.

    • NewSCIM 2.0 endpoint and just-in-time provisioning. Beta — opt in via Workspace → Members → Provisioning.
    • SecuritySAML metadata refresh added to the deployment pre-flight gate (followed the 52-day-ago SSO incident).
    • ImprovedAuth audit log surfaces SCIM provisioning actions distinct from interactive admin actions.
  5. 2026-02-25
    v0.8.1
    Release

    Bulk export and project-level retention.

    Workspace owners can age out projects automatically, schedule bulk exports (JSON/CSV/DOCX/PDF) on a cadence, and pre-flight delete with a signed receipt.

    • NewProject retention policies (90/180/365 days, custom, never) with grace-period notifications.
    • NewScheduled bulk export to S3, GCS, or signed URL.
    • NewSigned deletion receipt issued for any in-product or API-driven account/project/recording deletion.
  6. 2026-02-11
    v0.8.0
    Release

    Q&A copilot, citation-mode default.

    Citation mode is now the default for the Q&A copilot. Every answer carries provenance — transcript line, speaker, and timestamp — by default. The previous “summary” mode is still available but is opt-in.

    • NewCitation mode default: every answer cites at least one transcript line, with speaker and timestamp. No silent paraphrases.
    • BreakingAPI: the v1/answers endpoint citations[] field is no longer optional. Existing integrations expecting a flat string answer should switch to answer.text and iterate citations[]. The legacy shape continues to be served until 2026-07-01 (90+ day deprecation window).
    • ImprovedHallucination guard: when the answer cannot be grounded in cited evidence, the copilot says so explicitly rather than guessing.
    • APINew field on answer.text: confidence ∈ {high, medium, low, ungrounded}.
  7. 2026-01-30
    v0.7.6
    Release

    Workspace audit log, customer-facing.

    Every authentication, configuration, sharing, and export event is now visible to workspace owners as a streaming, filterable feed. CSV/JSON export and a webhook are included.

    • NewAudit log UI in Workspace → Trust → Audit. 12 months default retention; configurable on Team+; longer custom on Enterprise.
    • APIGET /v1/audit/events with cursor pagination and a streaming variant.
    • ImprovedRecordings: deletion events and deletion-receipt download links now appear in the audit log.
  8. 2026-01-15
    v0.7.5
    Release

    Speaker-aware transcription.

    Speaker diarisation is now on by default for new recordings. Speaker labels propagate to citations, exports, integration pushes, and search facets.

    • NewDiarisation on by default. Speakers can be re-labelled in the transcript editor; rename propagates everywhere.
    • NewSpeaker filter in the search panel.
    • ImprovedTranscript editor: keyboard shortcuts for fast speaker re-assignment (j/k to navigate utterances, 1–9 to assign).
Earlier releases (0.7.4 and prior) are available on request — product@citesvue.com.
Stay informed

Three ways to follow shipping.

  • RSS / Atom

    changelog.rss · changelog.atom — the same entries, formatted for your reader.

  • Monthly digest

    A single email per month. Highlights, breaking changes, security notes. Opt in once.

  • In-product banner

    Workspace owners see a banner the first time a new version unlocks a feature affecting their tier.

API & deprecation policy

Predictable change. Clear runway.

  • Additive changes. No notice required. New endpoints, new fields, new event types — never breaks existing integrations.
  • Behavioural changes. Communicated in the changelog. Where the change is observable, an opt-in flag is provided for one minor version before becoming default.
  • Breaking changes. 90+ days’ notice — emailed to workspace owners with API tokens, surfaced in response headers (Sunset / Deprecation), and called out in the changelog with the cutover date.
  • Security advisories. Material vulnerabilities are disclosed coordinated — see the security policy on /security. Routine patches ship continuously and may be omitted from the changelog.
See /status for live operational state and post-incident reports.
Related

Where to look next.