[depSync] Dependency Update: @actions/core

[github-actions]

Dependency Update Required: @actions/core

depSync detected an outdated dependency and prepared a compact remediation context for stateless follow-up automation.

Impact

• Latest version: 3.0.0
• Current versions: ^1.11.1
• Risk level: HIGH

1. Summary

The @actions/core dependency is structurally widespread throughout the depsync service. It is extensively utilized across core workflows, infrastructure logic, and test suites. Its primary responsibilities include GitHub Action input extraction (getInput) and execution state/logging management (info, warning, error, setFailed, debug).

2. Risk

The migration risk is moderate. While the method invocations themselves are functionally simple, the lack of isolation means any API signature changes could cause systemic workflow failures. The highest-risk files are src/index.ts and src/workflows/scan.workflow.ts, as they govern primary execution flows, input resolution, and failure state handling. Other significant risk vectors include src/clients/jules.ts and src/workflows/chatops.workflow.ts.

3. Recommended migration focus

• Primary Execution Contexts: Prioritize src/index.ts and src/workflows/scan.workflow.ts to guarantee foundational inputs and status reporting continue functioning correctly.
• Action Workflows & Clients: Review src/workflows/chatops.workflow.ts and src/clients/jules.ts for any breaking changes to logging or warning mechanisms.
• Dependency Injection Types: Update the dependency type mappings in src/clients/notifier.ts and src/core/scanner/scanner.ts to reflect any new API definitions.
• Test Suite Mocks: Audit and update the mocks in src/__tests__/index.test.unit.ts and src/clients/__tests__/jules.test.unit.ts to match the updated dependency behavior.

Affected Packages

Package	Description	Footprint
depsync	No description	13 files

ChatOps Commands

• /fix: Rebuild focused context, generate code changes, and open a Pull Request.
• /close: Close the issue and clean up any legacy session state if present.

This issue was generated by depSync.

[danielrispler]

/close