Repository navigation
Bump mbranicky/jira-dashboard to 1.3.2 - #2567
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Jira Sprint Workspace 1.3.2 is approved and merging, @mbranicky. Nothing is needed from you, and I made no edits.
Before and after: dragging an issue that already has a linked workspace now moves it in Jira without asking for a destination or starting another agent, and the card moves immediately and rolls back if Jira rejects it. The Paseo range widens to 0.16.x.
Review data
- Artifact: npm
paseo-jira-sprint-workspace@1.3.2(latest dist-tag). Downloaded tarball SHA-512 matchesartifact.integrityand the npm registry value. The package has npm provenance, and the recordedrepository.commitpassed the validator's provenance check. No absolute or..paths in the archive. - Compared against 1.3.1 file by file. Code changes:
server/moves.ts,shared/moves.ts(newexistingWorkspaceandjiraOnlyfields),index.server.ts(checks for an existing workspace link using the same workspace lookup the board already uses, in parallel with the board read), and optimistic-move state inclient/dashboard.tsxandclient/moves.tsx. AjiraOnlymove is rejected if the issue no longer has a linked workspace. Addedassets/move-pending.png. Overview andpaseo-plugin.jsonchange only the supported Paseo range. - Dependencies and build:
npm-shrinkwrap.jsonchanges only the version.package.jsonchanges only version and file list. The build isnpm ci --omit=dev --ignore-scriptsandscripts/prepare-native.mjs, which is unchanged from 1.3.1. No new network destinations, subprocesses or credential access in the changed files. - Validation:
node scripts/validate.ts --online --changed --base origin/mainpassed, and the PR's Validate check passed on this head. REVIEW.md blob3c5e763. - Not inspected: the plugin was not run. Unchanged 1.3.1 code was not re-reviewed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mbranicky/jira-dashboard: 1.3.1 → 1.3.2
@mbranicky, this update is ready for review. The published version stays unchanged until approval.
Artifact and validation details
Package:
paseo-jira-sprint-workspace.{ "previous": { "kind": "npm", "package": "paseo-jira-sprint-workspace", "version": "1.3.1", "resolved": "https://registry.npmjs.org/paseo-jira-sprint-workspace/-/paseo-jira-sprint-workspace-1.3.1.tgz", "integrity": "sha512-BVfcwze325hB/454tWgznKL7vxVmv1YpFrEneN4G6UQzF2UMBqcS71ZyrSKKFJbYeRV0rZCNyKV08lJuN8R/Dg==" }, "proposed": { "kind": "npm", "package": "paseo-jira-sprint-workspace", "version": "1.3.2", "resolved": "https://registry.npmjs.org/paseo-jira-sprint-workspace/-/paseo-jira-sprint-workspace-1.3.2.tgz", "integrity": "sha512-CmuXpqkjtw6xvtyol+Hl0HjaZa9SyjU5ZmjWymM2q/yyXYTJ9mg7b8lAcG/HhOTBQHfr30tjlNnwkFAufcRHiA==" } }Inline validation passed: tests and artifact checks. Run
node scripts/validate.ts --online --changedon the completed listing before merging. The default GITHUB_TOKEN does not trigger the PR validation workflow.Artifact diff
-For an existing npm installation, run
paseo plugin update paseo-jira-sprint-workspace --version 1.3.1. See the release notes and version tags.+For an existing npm installation, run
paseo plugin update paseo-jira-sprint-workspace --version 1.3.2. See the release notes and version tags.What you can do
@@ -44,7 +44,7 @@
Get started
-Requires Paseo 0.14.x or 0.15.x, Jira Cloud, and a scoped Jira API token, Teamwork Graph CLI OAuth, or Atlassian MCP OAuth. The verified Paseo host is macOS on Apple silicon. Linux has automated test coverage on Ubuntu. Windows and Intel Mac hosts are unverified. Compatibility has been checked with Paseo 0.14.0, 0.15.0 and 0.15.2. Use Node 24 and npm on the daemon host; Git is required for worktree isolation.
+Requires Paseo 0.14.x, 0.15.x or 0.16.x, Jira Cloud, and a scoped Jira API token, Teamwork Graph CLI OAuth, or Atlassian MCP OAuth. The verified Paseo host is macOS on Apple silicon. Linux has automated test coverage on Ubuntu. Windows and Intel Mac hosts are unverified. Compatibility has been checked with Paseo 0.14.0, 0.15.0, 0.15.2 and 0.16.0. Use Node 24 and npm on the daemon host; Git is required for worktree isolation.
To install from the public repository, run:
@@ -56,13 +56,13 @@
paseo plugin install "$PWD"