Declare `diff` as a direct dependency

[rak-phillip]

FileDiff.vue imports createPatch from diff, but diff is a transitive dependency. In the past, we've experienced breakages when transitive dependencies changed without notice. We also want to keep our dependency policy explicit for improved security and maintenance.

Proposed solution

Add diff as an explicit dependency in the package.json for Dashboard root and shell/.

Acceptance criteria

• diff is declared as a dependency for both the root package.json and in shell/
• FileDiff.vue continues to work as expected

[github-actions]

🎯 Agentic Issue Triage

Summary: shell/components/FileDiff.vue imports createPatch from diff, but diff is only a transitive dependency — not declared in either root package.json or shell/package.json. This is a clean-up task to make the dependency explicit, improving stability and supply-chain security.

📋 Analysis

• Type: Tech debt / dependency hygiene
• Affected file: shell/components/FileDiff.vue (only consumer of diff in the codebase)
• Risk: Low — diff is already present at runtime via a transitive dep; adding it explicitly doesn't change behavior, but protects against future silent removals/version bumps
• Milestone: v2.15.0

🔧 Implementation Steps

1. Find the version of diff currently resolved:

   cat node_modules/diff/package.json | grep '"version"'

2. Add diff to dependencies in the root package.json:

   yarn run add:no-lock diff

3. Add diff to dependencies in shell/package.json:

   cd shell && yarn run add:no-lock diff

4. Verify FileDiff.vue still compiles and functions correctly (render a diff in the UI, e.g., via the Git commit diff view).
5. Run unit tests: yarn test:ci
6. Run linter: yarn lint

✅ Acceptance Checklist

• diff added to root package.json dependencies
• diff added to shell/package.json dependencies
• FileDiff.vue renders correctly (no runtime errors)
• yarn test:ci passes
• yarn lint passes

🔗 Relevant Resources

• shell/components/FileDiff.vue — the only file importing from diff
• [diff npm package]((www.npmjs.com/redacted) — check latest stable version compatible with current usage of createPatch
• [OWASP Dependency management]((owasp.org/redacted) — rationale for explicit dependency declarations

Generated by Agentic Triage for issue #17401 · ● 201.3K · ◷

[github-actions]

🤖 Issue grooming analysis

This issue is well-groomed and ready for triage. Here's the analysis:

✅ Clear Problem Statement
The title and description clearly explain that diff is currently a transitive dependency used by FileDiff.vue (via createPatch). The motivation for declaring it explicitly — past breakages from transitive dependency changes, security, and maintenance policy — is well articulated.

✅ Acceptance Criteria
A concrete, testable checklist is provided:

• diff is declared as a dependency in both the root package.json and in shell/
• FileDiff.vue continues to work as expected

✅ Technical Details
The specific file (FileDiff.vue), import (createPatch), package (diff), and target locations (package.json in root and shell/) are all identified.

✅ Reproducibility / User Story
Clear task framing: make diff an explicit dependency to prevent silent breakage from transitive changes. This is a well-scoped tech-debt task with a straightforward implementation path.

This analysis was generated automatically based on the repository's grooming checklist.

Note

🔒 Integrity filter blocked 8 items

The following items were blocked because they don't meet the GitHub integrity level.

• Screen not refreshing after updates #17298 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [AI] Create E2E test automation for rancher-ai-ui #17107 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Bug: "Mark all as read" button in Notification Center wipes URL hash fragment #16923 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Support configuring cpu model when creating harvester guest cluster #16187 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Spacing is wrong on node pools section when provisioning/editing EKS cluster #13888 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Cluster Drivers list is not displaying the drivers in first access from a selected driver #13297 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• UI should display clear permission denied error messages #11263 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Rename Azure AD to Entra ID #9963 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Issue Grooming · ● 397.5K · ◷