Skip to content

Windshift v0.8.5

Latest

Choose a tag to compare

@stefan-ernst stefan-ernst released this 14 Aug 13:16
· 3 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.8.5
1a539d8

Windshift 0.8.5

Windshift 0.8.5 is a checkpoint release. You will have to upgrade to this release from earlier version before moving to versions 0.8.6 and later.

Agent Studio, safer upgrades, and easier work across workspaces

Agent Studio and AI

  • Create and manage agents in one place: Agent Studio brings Standard and
    Coding agents into a shared catalog with guided creation, clear readiness,
    private testing, run history, and focused controls for instructions,
    knowledge, tools, access, and runner setup. Existing coding-agent bindings continue
    to work without conversion. (WI-846)
  • Tailor the agent catalog: System administrators can create, edit, and
    disable agent templates while the built-in catalog remains available as the
    default. (WI-922)
  • Better model support: Windshift now uses a provider-neutral
    inference contract via the Fantasy Library with native OpenAI Responses and Anthropic support across
    built-in and coding agents.
    (WI-903, WI-904, WI-920, WI-921)

Workspaces and everyday work

  • Move work between workspaces: Work items can move between workspaces
    through a preview that explains remapped and dropped fields and assigns a new
    destination key. Page trees can also move between workspaces from the UI,
    API, or ws CLI, and pages can be reparented directly in the tree.
    (WI-888–WI-890, WI-926)
  • Better custom fields and boards: Checkbox fields now use real boolean
    values across work items, assets, portals, imports, CQL, and board cards.
    Board card configuration also separates system from custom fields and links
    straight to custom field administration, so it is clear where a field comes
    from and why it is not on a card yet. (WI-891, #156, #160)
  • Predictable memory: Server and cache memory now share an
    explicit budget, expose clearer diagnostics, and stay bounded under the
    qualified 100-user, 100,000-item workload. (WI-870–WI-874, WI-895)

Upgrade and security

  • 0.8.5 is the required upgrade bridge for older databases. Back up before
    upgrading. This release converts every supported legacy SQLite or PostgreSQL
    database to the canonical schema and records a durable checkpoint. Future
    releases will require that checkpoint, so installations older than 0.8.5
    must upgrade through 0.8.5 first. Item ranking now rebalances online with
    resumable, operator-visible recovery. (WI-930, WI-931, WI-981–WI-984, WI-995)

Issues fixed thanks to your reports

  • Links pasted into a work item description or comment are kept instead of
    being stripped when the content is saved. (#166)
  • Access tokens can be created with an expiration date again. Expiry is now a
    calendar date that ends at the start of the following day in your configured
    timezone. (#182)
  • API tokens can grant the time tracking and test management scopes from the
    token dialog, so MCP clients no longer fail with a missing time:read or
    tests:read scope. (#172)
  • Clearing notifications now sticks: cleared notifications no longer come back
    after a page refresh. (#190)
  • Deleting a work item no longer shows an error toast for a deletion that
    actually succeeded. (#189)
  • Diagrams can be deleted again from work items and pages. (#188)
  • Saving workspace settings no longer resets the workspace avatar and other
    settings that were not part of the change. (#191)
  • Quick add on the board offers only the workspaces and item types the
    collection and its configuration sets allow, instead of defaulting to an item
    type the workspace does not use. Changing the type on an existing item is
    still unrestricted and will follow. (#186)
  • Card field visibility supports real drag-and-drop ordering. (#159)
  • Model tests against OpenAI models that require the newer completion token
    parameter no longer fail with a max tokens error. (#163)
  • WEBAUTHN_RP_ID and ALLOWED_HOSTS now accept a full https:// URL and keep only
    the parts WebAuthn needs, so a reverse-proxy setup configured that way no
    longer produces an invalid relying party ID. (#158)