DoDiODev opened a new pull request, #9199:
URL: https://github.com/apache/devlake/pull/9199

   ### Summary
   
   `e2e/` has been a Dependabot `npm` directory since #9089, but it only 
contains a `package.json` with a caret range and no lockfile. Every install 
therefore resolves whatever Playwright release is current, and Dependabot has 
to guess the version it is updating from — #9098 was titled "bump 
@playwright/test from 1.63.0 to 1.62.1" although it actually raised the range 
from `^1.58.2` to `^1.62.1`.
   
   This PR commits a lockfile and updates the related Dependabot comment.
   
   ### Changes
   
   | File | Change |
   |---|---|
   | `e2e/package-lock.json` | New, lockfileVersion 3, public npm registry. 
Resolves `@playwright/test` `^1.63.0` to `1.63.0` (plus `playwright`, 
`playwright-core`) |
   | `.github/dependabot.yml` | The `/e2e` comment no longer says "this 
directory has no lockfile". `versioning-strategy: increase` stays so the 
declared range and the locked version move together |
   
   Why npm: `e2e/package.json` is the `npm init` scaffold and declares no 
`packageManager`; `npm ci` works with any Node installation. `**/*.json` is 
already excluded in `.licenserc.yaml`, so no license-config change is needed.
   
   No change to `package.json`, test code or any workflow.
   
   ### Verification
   
   | Check | Result |
   |---|---|
   | `npm ci` from the committed lockfile | ✅ 3 packages, `playwright 
--version` → 1.63.0 |
   | `resolved` URLs | ✅ all `https://registry.npmjs.org/` |
   | `skywalking-eyes header check` | ✅ |
   | Unmodified upstream workflows in the fork on top of current `main` | ✅ all 
8 green, incl. 
[`e2e-mysql`](https://github.com/DoDiODev/devlake/actions/runs/37469233832/job/112288055144)
 and 
[`e2e-postgres`](https://github.com/DoDiODev/devlake/actions/runs/37469233832/job/112288056166)
 |
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to