github Windshiftapp/core v0.9.5
Windshift v0.9.5

31 minutes ago

Windshift 0.9.5

Windshift 0.9.5 reworks time tracking around one place to log work. You can open the time-log form from
anywhere in the app, start and stop a timer from the Time & Projects sidebar entry, and run a timer without
a project. When a stop already has the information a worklog needs, the entry is booked in one step;
otherwise it is saved as a recoverable draft that stays out of reports and item totals until you complete or
dismiss it.

Action flows gained a JavaScript node that can call the v2 REST API as the action's executor. The script
never sees the credential it acts with: Windshift issues a short-lived token for the executor, accepts only
relative v2 paths, and applies the same permission checks as a normal API client, so a script can never act
with more permission than its executor has. Action definitions are now versioned, and each run records the
revision it used. Actions can also be renamed and duplicated, and the canvas previews are driven by live
metadata.

Deployment owners can apply an operator-owned policy file that denies capabilities and sets instance-wide
ceilings without forking the application or changing organization preferences. The policy is read at
startup, requires a restart to change, and cannot be edited through the API.

Imports grew on two fronts. A new plane-import command loads a Plane export while preserving item
numbers, authors, and timestamps, and the Jira importer gained Data Center workflow, screen, and Assets
support through a read-only companion plugin. Sign-in added GitHub alongside OIDC, and customer portals can
now restrict access to named organizations and to customer-only identity providers.

The frontend received a performance and consistency pass: collection views stay fast with long lists, the
rich-text editor is no longer loaded at startup, locale catalogs load in parallel, and date pickers were
unified with a configurable week start. A hand-written Dutch locale joins the built-in languages, and the
design system received an accessibility pass.

Highlights

Time tracking from one surface

Time logging no longer depends on being on a particular page. The command palette, item detail, the /time
page, mobile, and keyboard shortcuts all open the same form in place, so logging work never interrupts
navigation. The Time & Projects sidebar entry is now a dropdown with a start/stop timer, project search, a
drafts badge, and navigation (GitHub #496).

A timer can start without a project. On stop, the worklog is booked directly when project, description,
date, times, and duration are all present; when they are not, the incomplete entry is saved as a user-owned
draft. Drafts are recoverable from the sidebar badge, stay out of reports, item logged time, and briefings,
and live until you complete or dismiss them. A retried stop cannot double-book, and the v1 timer contract is
unchanged.

JavaScript action nodes with executor-scoped API access

An execute_script node runs JavaScript and can call the v2 REST API as the action's executor. The script
never sees the credential it acts with: Windshift issues a short-lived token for the executor, accepts only
relative /rest/api/v2 paths, and applies the same permission checks as a normal API client, so a script
can never act with more permission than its executor has. Execution stays bounded by timeouts, budgets, and
cancellation, and every change carries action and execution attribution (WI-2174, WI-2178).

Every save of an action now creates a revision, and each execution records the revision it ran, so you can
see exactly what ran and when. Revision history is browsable in the editor. Changing the executable
configuration of a privileged action requires action.set_actor, so editing a script is treated as
delegated code execution (WI-2173). Actions can also be renamed and duplicated from the manager (WI-2168,
WI-2170), and the flow editor previews are driven by live metadata (WI-2254).

Operator controls for deployment owners

A new operator-owned JSON policy file, loaded at startup with --operator-policy or
WINDSHIFT_OPERATOR_POLICY, lets a deployment owner deny capabilities and set instance-wide ceilings. The
deny list covers instance lifecycle, maintenance, runtime diagnostics, plugin execution, LDAP, server
scripts, imports, generic mail, and AI; limits covers attachment and blob bytes, concurrent requests and
streams, requests per minute, automation steps per day, mail recipients per day, and AI tokens per day.
Managed mail mode, AI model allowlists, and an optional import admission directory are configured in the
same file. Unknown fields, invalid capabilities, and negative ceilings reject startup, and the file cannot
be edited through the API (WI-2175).

Denied capabilities return 403 operator_restricted; storage ceilings return 413 operator_limit_exceeded;
work admission returns 429 operator_limit_exceeded with Retry-After. Usage is counted across restarts,
so a restart does not grant a fresh allowance, and an unavailable required budget store fails closed.
Effective controls are readable by system administrators, while public capability discovery exposes only
denials and mail mode.

Plane and Jira Data Center imports

plane-import loads a JSONL contract produced from a Plane database into a Windshift workspace. It
preserves the source's item numbers, authors, timestamps, states, priorities, and labels, restores comments
and parent links, and keeps a mapping of imported records so a re-run updates its own rows instead of
duplicating them. Rows edited in Windshift since import are left alone, and number collisions the importer
does not own fail loudly. The command runs the migration catalog first unless --skip-migrate is passed,
and prints a JSON report (#379).

For Jira Data Center, a read-only companion plugin exposes workflow graphs and guards, screen schemes, and
Assets over an admin-only REST surface that the public DC API does not provide. The importer prefers the
companion and falls back to the public API when it is absent. Data Center Assets are read through the
legacy Insight API, and Assets import is now opt-in: choose schemas in the import wizard, and selecting none
imports nothing and records jira_assets_not_selected (WI-2059, WI-2069, WI-2070, WI-2078). Saved-filter
discovery is scoped to the target workspace, and Cloud workflow conditions now decode whether the source
sends an array or an object (WI-2079).

GitHub login and customer access policies

GitHub is available as a login provider alongside OIDC, for both the main application and customer portals.
A provider can require membership in a named GitHub organization, and sign-in requires a verified email and
never requests repository scopes (#501).

Customer portals gained customer-only identity providers and resource-scoped access. A customer-only
provider admits portal customers rather than internal users, and a resource such as a board carries an
access policy with mode public or an organization allowlist, so admission is decided independently of
content visibility. Existing self-managed deployments are unaffected until a provider or policy is
configured.

Boards, portals, and sharing

Boards can be published to a portal channel as a placement with its own label and an audience that is
independently narrower than the standalone public link. External publication and standalone availability
are now separate settings, with a sharing history, a revoke reason, and an allow-republish path. Owners and
system administrators get a Public Boards management page listing each publication with its audience,
locations, and sharing history (WI-2240).

The customer portal gained a Compact experience that composes modules, including placed boards, requests,
forms, knowledge base, drafts, approvals, and profile, with a configurable navigation order.

Frontend performance and consistency

Collection views stay fast with long lists and no longer need a virtualization preference (WI-2147). List
and backlog gained the board's multi-select mode and the same bulk action toolbar, so all three views offer
identical selection and bulk actions.

The rich-text editor is no longer loaded when the app starts. It loads only when needed and shows a clear
error with a Reload action if it fails. The startup JavaScript dropped by roughly 516 KB raw and 159 KB gzip
(WI-2144). Locale catalogs now load in parallel, so a non-English interface starts fetching while English is
still pending (WI-2150). SLA badges and panels now refresh only what changed and keep the right scope when
several workspaces update at once (WI-2112).

Date pickers were unified behind one calendar-aware implementation, a date-time picker was added, and
regional settings gained a week-start preference that the picker, roadmap, and weekly calendar follow. The
design system received an accessibility pass covering focus, contrast, typography, and motion (WI-2221), and
modal focus and keyboard ownership were unified so only the topmost dialog responds (WI-2222, WI-2224).

Also in 0.9.5

  • Dutch language pack. A Dutch (Nederlands) translation joins the built-in languages with
    full key coverage, including Dutch date formats for backend-rendered email, so the interface no longer
    falls back to English (#532).
  • Configurable backlog row fields. Backlog rows can show a chosen set of fields, selected from a picker,
    instead of a fixed layout (#490).
  • Agent run indicator. The comments tab shows a live indicator above the thread: a green dot with "Agent
    running" while a runner works, or a grey dot with "Agent queued" while it waits. Clicking opens the Agent
    log tab.
  • Raw Markdown editor plugin. A reference editor.markdown provider edits a surface as exact Markdown
    source in a plain textarea, for cases where the WYSIWYG editor's source normalization is not wanted.
  • Roadmap fixes. Dependency arrows render reliably, and task previews open the correct item (#487).
  • Local LLM endpoints. API paths no longer gain a duplicate version segment, so local and
    OpenAI-compatible endpoints resolve correctly (#528).
  • Test authoring tools. Agent-driven QA workflows add test case authoring skills and AI tools for
    creating, updating, archiving, and bulk-editing test cases, plus item test coverage reads (WI-2184).
  • PostgreSQL SSL fallback modes. Split connection variables accept lib/pq's SSL modes, and direct
    connection strings keep their own sslmode (WI-2105).
  • Explicit configuration wins. Explicitly supplied flags and USE_PROXY=false are honored instead of
    being overwritten by defaults or auto-detection (WI-2093, WI-2098).
  • Database request limits. Ordinary v2 database work is bounded by DB_REQUEST_TIMEOUT, uploads start
    their budget after the body is received, and read cursors are released before nested reads (WI-2096,
    WI-2101, WI-2104).
  • Passkeys. The session remember-me choice survives passkey authentication, and policy-aware login
    handles provider restrictions and mandatory-passkey rollouts safely (WI-2214 through WI-2220).
  • Smaller fixes. Collection backgrounds persist across view switches, the list title opens the item
    instead of renaming it, only one menu surface opens at a time, the workspace sidebar closes from a hover
    control and toggles from its resize bar, personal tasks route to the task modal, worklog business dates
    are preserved, Zammad uses a scalable workspace picker, and the overview chart uses complete date-bounded
    aggregates.

Security

  • All outbound HTTP now goes through one SSRF-safe transport that honors configured proxies, and the S3
    client follows the same outbound TLS policy (WI-2091, WI-2092).
  • OIDC login is bound to a nonce (WI-2099), a TLS key pair that cannot be loaded fails startup (WI-2095),
    and an unusable PLUGIN_LICENSE_PUBKEY fails startup instead of silently disabling license enforcement
    (WI-2107).
  • Plugin installation, execution, and asset serving were hardened: manifest identity is validated, installs
    stage and atomically promote with rollback, per-prefix asset auth is declared and enforced, http_fetch
    responses are bounded, and replaced runtimes and schedules are closed (WI-2049).
  • Action scripts act only as their executor, keep credentials out of the script, accept only relative v2
    paths, and share the instance script limit (WI-2174, WI-2178).
  • Anonymous OAuth registration is capped, and configuration-set migration fails closed when authorization or
    validation fails.

Bug fixes

  • Jira import correctness. Authentication, payloads, media, and Data Center contracts were aligned; typed
    Assets scalars and page exhaustion were corrected; Data Center wiki markup converts and attachment media
    resolves; request types and portal customers are classified; and the guarded-transition readiness reason
    is accurate (WI-2059, WI-2069, WI-2070).
  • Items and history. Item history resolves all reference ids and creator and workspace names, and asset
    titles are gated by asset-set access (GH #451). custom_field_values is cast when read on PostgreSQL.
  • Mobile and timers. Mobile refreshes worklogs after shared time-log saves, and the timer resolves its
    workspace only from authoritative context (WI-2264, WI-2265).
  • Boards and collections. Board configuration reads are shared, navigation is preserved on save and
    reset, the header renders while items load, missing totals start after superseded initial loads, and fresh
    install schemas include board placements (WI-2201, WI-2202, WI-2143).
  • Plugins and upgrades. Installed plugin licenses are retained across staged upgrades, source membership
    is retained through combined configuration migrations, and object translation locales are discovered
    automatically (WI-2266, WI-2267).
  • Command palette and modals. Palette search and keyboard activation were corrected, controlled popups
    stay inside inline click boundaries, popup navigation is handled before modal key handlers, and login
    return paths are consumed before dialog teardown.

Upgrade notes

  • Operator controls are optional. Set WINDSHIFT_OPERATOR_POLICY or --operator-policy to a JSON file to
    apply a policy. Omitting it keeps self-managed behavior, and zero ceilings add no limit. Changes require a
    controlled restart. Read the effective controls at the authenticated administrator endpoint before
    relying on them.
  • Schema migrations run automatically. This release adds plane_import_mappings; the
    sso_providers.github_organization, account_type, and customer_organisation_id columns; the
    sso_state_tokens.resource_kind and resource_id columns; the customer_resource_access,
    customer_external_accounts, customer_resource_sessions, and customer_resource_tokens tables;
    user_sessions.remember_me; the action_definition_revisions table plus actions.current_revision_id
    and action_execution_logs.definition_revision_id; time_worklog_drafts and time_worklog_bookings;
    operator_usage; the collections board-publication and sharing columns; and the board_placements
    table. active_timers.project_id becomes nullable. No configuration change or re-login is required.
  • Action executions bind to revisions. Existing actions are migrated to a current revision. Editing an
    action's executable configuration on a privileged action now requires action.set_actor, and revision
    history is available through v2 and the editor.
  • Time tracking adds v2 endpoints. /time/timers, /time/timers/active/stop, and the
    /time/worklog-drafts endpoints are new. The v1 timer contract is unchanged and remains complete-only.
  • GitHub login needs a provider. Configure a GitHub SSO provider to offer the button, and optionally set
    an organization restriction. Customer-only providers use the new account_type, and resource access
    policies default to unrestricted until set.
  • Assets import is opt-in. Selecting no Assets schema imports nothing and records
    jira_assets_not_selected; choose schemas in the Jira import wizard to import them.
  • Plane import is a separate command. Run plane-import against the target database and workspace with
    the JSONL contract, users file, and optional aliases. It runs the migration catalog unless --skip-migrate
    is passed.
  • PostgreSQL SSL modes. Split-variable configuration now validates against lib/pq's supported modes;
    connection strings are unaffected.

Thank you

Thank you to Faks (@Faks) for the Plane importer
(#379).

Thank you to Michel Jelsma (@mijelsma) for configurable backlog row fields
(#490).

Thank you to Toofan Mohammadi (@mrtfn) for the roadmap dependency arrow and task
preview fixes (#487).

Thank you to Luqman Rizal (@luqmanrizal) for the local LLM endpoint fix
(#528).

Don't miss a new core release

NewReleases is sending notifications on new releases.