Skip to content

fix: sync package-lock.json and repair snyk-security workflow - #63

Draft
Mapuppy09 with Copilot wants to merge 2 commits into
snyk-fix-11e19bf9fba064c3844409ecf388566efrom
copilot/fix-with-copilot
Draft

fix: sync package-lock.json and repair snyk-security workflow#63
Mapuppy09 with Copilot wants to merge 2 commits into
snyk-fix-11e19bf9fba064c3844409ecf388566efrom
copilot/fix-with-copilot

Conversation

Copilot AI commented Jul 30, 2026

Copy link
Copy Markdown

The snyk-security CI job was failing due to three compounding issues introduced when the Snyk bot updated workspaces/libnpmteam/package.json to fix SNYK-JS-TAR-18319500.

Changes

  • package-lock.json: Regenerated via npm install --package-lock-only to sync with workspaces/libnpmteam/package.json requiring npm-registry-fetch@^18.0.1 (lock file still referenced 17.1.0, causing npm ci to fail with EUSAGE)

  • .github/workflows/snyk-security.yml:

    • github/codeql-action/upload-sarif@v2@v3 (v2 is deprecated and was erroring)
    • Added --sarif-file-output=snyk.sarif to Snyk action args — without this flag, Snyk does not emit the SARIF file, so the upload step always failed with "Path does not exist"

@snyk-io

snyk-io Bot commented Jul 30, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

- Update package-lock.json to sync with workspaces/libnpmteam/package.json
  which requires npm-registry-fetch@^18.0.1 (updated by Snyk bot)
- Upgrade github/codeql-action/upload-sarif from v2 to v3 (v2 deprecated)
- Add --sarif-file-output=snyk.sarif to Snyk action args to generate SARIF file
Copilot AI changed the title [WIP] Fix issues identified in Copilot actions run fix: sync package-lock.json and repair snyk-security workflow Jul 30, 2026
Copilot AI requested a review from Mapuppy09 July 30, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants