Repository navigation
Certify pm-jira on PM CLI 2026.10.4 and consolidate pending dependency updates - #126
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 31 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (3)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (3)
📒 Files selected for processing (11)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThis change updates dependency and workflow versions, adjusts the merge-driver package probe, registers Jira import and export flags, and adds tests and certification records for PM CLI/SDK 2026.10.4. ChangesJira CLI certification
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other Merge Risk: ⚪ Minimal · up to The dependency updates, Jira flag registrations, and merge-driver probe have no identified merge-blocking issue. Live Jira connectivity remains outside the reported certification scope. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 5 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Reviewer's GuideThis PR certifies pm-jira against PM CLI/SDK 2026.10.4 by consolidating exact dependency and automation pins, wiring native Jira importer/exporter flags through the supported SDK contract, hardening merge-driver lookup handling, and documenting the passing release, packed-package, and cross-runtime acceptance results. Sequence diagram for native Jira flag registration and executionsequenceDiagram
participant CLI as PM_CLI
participant SDK as PM_SDK
participant Extension as pm_jira
participant Jira as Jira_Pipeline
CLI->>SDK: registerFlags(jira import, PULL_FLAGS)
CLI->>SDK: registerFlags(jira export, EXPORT_FLAGS)
CLI->>Extension: jira import or jira export
SDK->>Extension: invoke registered handler
Extension->>Jira: runImport or runExport
Jira-->>CLI: command result
Flow diagram for packed cross-runtime acceptanceflowchart LR
Source["pm-jira source"] --> Pack["npm pack"]
Pack --> Workspace["Copied real tracker workspace"]
Workspace --> Npm["PM CLI 2026.10.4 via npx"]
Workspace --> Bun["PM CLI 2026.10.4 via native bunx"]
Npm --> Compare["Compare JSON results"]
Bun --> Compare
Compare --> Verify["Verify nine items and pushed:false"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Re this comment: This is an automatic-review eligibility skip for a repository below the star threshold, not a code review. A manual review request is being posted. No repository policy or gate was weakened to suppress it. |
|
Re this comment: Useful summary acknowledged. At a889967 both Node CI jobs pass, with the test-first native import/export flag repair and 195/195 local tests. Packed npm/native Bun exports all nine copied tracker items. Live Jira calls remain outside acceptance; no new actionable finding was supplied. |
|
Re this comment: Useful summary acknowledged. At a889967 both Node CI jobs pass, with the test-first native import/export flag repair and 195/195 local tests. Packed npm/native Bun exports all nine copied tracker items. Live Jira calls remain outside acceptance; no new actionable finding was supplied. |
|
Re this comment: This review body reports an exhausted review quota and supplies no source findings. It remains unavailable evidence, rather than approval; the reported tests and remaining blockers are independent. |
|
The edited review now covers a889967 with no actionable findings; acknowledged. Node 22 and 26 CI and both npm audits pass. The packed npm/native Bun receipt covers the copied tracker without live Jira authentication. This replaces the earlier automatic-skip assessment. Other unavailable reviewer evidence remains pending. |
|
Review command completion acknowledged; the substantive summary explicitly covers a889967 and reports no actionable findings. Node 22 and 26 CI and both npm audits pass. The packed npm/native Bun receipt covers the copied tracker without live Jira authentication. |
|
@coderabbitai review |
|
The newly edited summary skips automatic review of e2feba4 (fewer than10stars) while retaining its earlier source-candidate review. This skip is not approval of the final metadata head. Greptile independently reviewed the latest head; unchanged source receipts and earlier manual review remain scoped to their recorded SHAs. |
|
Acknowledged the updated substantive review explicitly covering e2feba4, with no new actionable findings. Known certification blockers remain documented; zero unresolved threads and green configured checks do not replace missing reviewer evidence. |
|
|
The re-review command was rate limited. This is unavailable review evidence, not approval. The earlier substantive source review remains scoped to its recorded commit; the final metadata head is independently covered by current CI and Greptile. |
|
The edited comment now explicitly rate-limits review of the final metadata diff. The retained no-actionable summary describes the earlier source candidate. This does not constitute exact-final-head review clearance; quota and missing reviewer responses remain open in the handoff. |
Pins PM CLI/SDK, pm-ops, pm-changelog and managed pm-github to 2026.10.4, with exact development dependency versions and the unchanged SDK floor. Consolidates Dependabot #118, #121, #122 and #123, including the exact CodeQL SHA/comment bump. Copies the published merge-driver launcher unchanged and adds a real malformed-lookup regression.
Packed real-tracker acceptance exposed unregistered native Jira importer/exporter flags. A new activation-contract test failed before the repair; existing pull/export definitions are now registered through the supported SDK, so documented CLI options reach their handlers without a parser bypass or new floor.
Validation (heavy commands serialized with the shared flock):
npm run release:checkthrough linkedpm test pm-jira-gdlw --run --progress, usingenv -u PM_PATHfor the CI child: 195/195 pass, zero skips.npm auditandnpm audit --omit=dev: zero vulnerabilities; no open Dependabot security alerts.npx pm health --strict-exit --require-merge-drivers: exit 0, one advisory stale-item finding.bun install --no-save: exit 0; no existing Bun lockfile is changed.npm packinstalled into the copied real project tracker. npm/npx and native Bun (bunx --bun @unbrained/pm-cli@2026.10.4): pass for validate, sync/import dry runs, ordinary export and rich/update-existing export. All nine real items exported, independently confirmed against a complete unbounded list, with the owner present and complete JSON parity; scratch deleted. Live Jira authentication/network calls are outside this acceptance.Exact commands and scope. PM owner pm-jira-gdlw stays open for orchestrator verification, merge and closure.
Summary by cubic
Certifies
pm-jiraon PM CLI/SDK 2026.10.4, consolidates the pending Dependabot updates into one branch, and records verified CI and reviewer evidence at the final head. This also fixes a regression where native Jira import/export flags were rejected by CLI 2026.10.4 because the package never registered them.Bug Fixes
PULL_FLAGSandEXPORT_FLAGSthrough the SDK schema API, sopm jira importandpm jira exportadvertise their documented flags without a parser bypass or floor increase.node_moduleslookup paths.Dependencies
@unbrained/pm-cli,pm-ops, andpm-changelogto 2026.10.4,@types/nodeto 26.6.4, and TypeScript to 7.0.2 without changing the existing CLI peer floor.pm-githubextension and CI restore pin to 2026.10.4, and adopts the exact CodeQL SHA from Dependabot; scheduled sync stays disabled.No migration steps are required. Full validation passes 195/195 tests with zero skips and unchanged 100% coverage thresholds. CI and reviewer evidence was verified at the exact head, with the certification item left open for orchestrator verification.
Written for commit e2feba4. Summary will update on new commits.
Summary by Sourcery
Certify pm-jira on PM CLI/SDK 2026.10.4 while consolidating dependency updates and repairing native Jira flag registration.
Bug Fixes:
Enhancements:
CI:
Documentation:
Tests: