chore: release - merge dev into main - #1529
Merged
Merged
Conversation
…1524) * fix(jira): paginate searchProjects() + make Combobox name-searchable * fix(ci): bump brace-expansion override to ^5.0.9 to clear high-severity audit npm audit --omit=dev --audit-level=high flagged brace-expansion@5.0.8 (GHSA-rgw5-rvv9-x895, DoS via unbounded intermediate arrays). Bump the existing override to ^5.0.9 so the transitive dependency (via @oclif/core -> minimatch) resolves to the patched release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Cascade Bot <bot@cascade.dev> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…G-1768) (#1528) * fix(jira): match status by locale-invariant ID with name fallback (MNG-1768) * fix(jira): skip jira_transition_not_found capture on benign no-op moves Address review feedback on PR #1528 (MNG-1768): - moveWorkItem no longer fires the jira_transition_not_found Sentry capture when the issue is already in the destination status. Best-effort callers (createWorkItem's backlog move, lifecycle moveOnPrepare/ moveOnSuccess) move unconditionally and JIRA offers no self-transition, so an already-there issue legitimately reaches the miss path — capturing there diluted the genuine locale/misconfig signal. Added isAlreadyInStatus helper (ID-first, name fallback) so only a real miss is surfaced loudly. - Dropped the vestigial `t.id === destination` (transition-ID) matcher branch that could collide with a numeric status-ID destination; no caller passes a transition ID. - Docs: src/integrations/README.md and docs/architecture/04-agent-system.md now reference resolvePMStatusAgentByIdOrNameFromWorkflowDefinitions for the JIRA status-changed trigger. - Clarified the overstated pm-status "prefers the ID match" test comment (per-entry ID-before-name, first matching entry wins during iteration). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(jira): match status by id-or-name in label-added and comment-mention (MNG-1768) The MNG-1768 write side persists locale-invariant JIRA status IDs into `jira.statuses`, but only status-changed dispatch and moveWorkItem were migrated to match by ID. Two other readers of the same map still matched the issue's `status.name` by name only, so they silently stopped firing for ID-based configs (all new projects, plus any re-saved project): - `JiraReadyToProcessLabelTrigger` (cascade-ready label flow) - `JiraCommentMentionTrigger.isInPlanningStatus` (planning gate) Add `resolvePMLabelAgentByStatusIdOrNameFromWorkflowDefinitions` (mirroring the shared status resolver), read `status.id` alongside `status.name` in both triggers, and gate planning by ID-first with a case-insensitive name fallback. Now every consumer of the ID-valued `jira.statuses` map is locale-invariant. Adds ID-config unit tests for each trigger and the new resolver, and documents the two readers in the MNG-1768 README subsection. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Cascade Bot <bot@cascade.dev> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
2 participants
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.
Automated release PR created by the release workflow.
Commits (2):