Skip to content

Jira Sprint Workspace 1.3.2

Latest

Choose a tag to compare

@mbranicky mbranicky released this 16 Nov 14:10
c1ed192
  • Move issues with existing workspaces without choosing a destination or restarting an agent. Jira-required fields and ambiguous transitions still prompt.
  • Move linked cards immediately while Jira processes the request, roll back on failure, and retain confirmed positions through stale refreshes.
  • Support Paseo 0.16.x while retaining 0.14.x and 0.15.x (>=0.14.0 <0.17.0). All three connection methods remain included: REST API, Teamwork Graph CLI OAuth and Atlassian MCP OAuth.
  • Add a synthetic pending-move screenshot and update release/compatibility documentation.

Install or update

paseo plugin install npm:paseo-jira-sprint-workspace@1.3.2
# Existing npm installation:
paseo plugin update paseo-jira-sprint-workspace --version 1.3.2

Verification

Final candidate: both typechecks, 327 backend tests, 257 browser tests, 15 release-verifier tests and source/package checks passed. The clean extracted manifest build and production audit passed with zero vulnerabilities. Exact 0.16.0 SDK checks and a separate macOS arm64 0.16.0 daemon verified activation, reload, settings rendering in the bundled web client, all three connection choices and display preference persistence. The user's live 0.15.4 desktop app/daemon were not changed. No live Jira writes.

The attached package and SHA256SUMS identify the exact tested artifact. Paseo catalog approval and deployment are separate from npm publication.

Preparation PR #50 · PR checks · Exact-main checks · Release commit

Publication verification

Published once through GitHub OIDC. npm processing outlasted the initial verification window; the verify-only run then passed without republishing. npm latest resolves to 1.3.2 and the published package matches the tested release artifact.

A fresh installation from npm:paseo-jira-sprint-workspace@1.3.2 into the separate Paseo 0.16.0 instance reports version 1.3.2, npm source and running status. The published settings surface renders correctly and retained the display preference across reinstall. The temporary instance was stopped after verification; the live installation was left unchanged.