chore(deps): update patch/minor dependencies - #855
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
5 times, most recently
from
July 19, 2026 17:04
a60a9e3 to
8f315cb
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
7 times, most recently
from
July 25, 2026 22:50
35efc3b to
f465e4f
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
8 times, most recently
from
August 4, 2026 16:36
3b0ab55 to
d31dd63
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
2 times, most recently
from
August 7, 2026 00:01
54060fb to
540838b
Compare
3 tasks
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
August 10, 2026 16:38
540838b to
032d09a
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
4 times, most recently
from
September 1, 2026 14:13
6a7842e to
59f3b58
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
3 times, most recently
from
September 3, 2026 20:32
4e8deff to
c129a21
Compare
l2ysho
added a commit
that referenced
this pull request
Sep 4, 2026
…son only Reviewer feedback on #906: relaxing the pnpm guard was not needed. The breakage came from `constraints.pnpm: "^11.0.0"` floating past the pin, so dropping that key is the whole fix. Revert `package.json` to master — `devEngines.packageManager` goes back to an exact 11.13.0 with `onFail: "error"`. Verified with a standalone pnpm 11.25.0 (what Renovate resolves) and npm 11.16.0: - ordinary PR branch, exact pin + onFail "error" -> exit 0. With `constraints` gone Renovate resolves 11.13.0 from `packageManager`, which matches the guard, so the artifacts step stops failing. - npm at the repo root -> exit 1, EBADDEVENGINES. `onFail` governs the package-manager *name* check too, so "warn" would also have stopped blocking `npm install` here, which bypasses every pnpm-only setting in pnpm-workspace.yaml: the 1-day minimumReleaseAge supply-chain gate, the allowBuilds postinstall allowlist and the @puppeteer/browsers override. Keeping "error" preserves that block. - a range (`^11.13.0`) also clears the guard, but pnpm string-compares `packageManager` against `devEngines.packageManager`, so it warns `"packageManager" will be ignored` on every command, and corepack rejects a range outright. Not worth it. One case still breaks by design: a Renovate PR that bumps `packageManager` alone leaves `devEngines` behind and aborts, as #855 does. That is now a single red PR instead of the whole queue, and it is fixed with a sync commit bumping both pins — the same way crawlee handles it (apify/crawlee#4050). Also add `rangeStrategy: "replace"`. Renovate's PinVersionsMigration already rewrote the removed `pinVersions: false` to exactly that, so this is behaviour-preserving; dropping the key without it would have fallen back to the `auto` default and changed how every range update is written. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
20 times, most recently
from
September 9, 2026 14:50
5c1bb27 to
2beb215
Compare
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
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.
This PR contains the following updates:
1.61.1→1.63.0v1.4.0→v1.5.03.13→3.14v10.0.1→v10.1.01.3→1.41.61.1→1.63.01.59.1→1.63.01.61.1→1.63.0Release Notes
microsoft/playwright (@playwright/test)
v1.63.0Compare Source
v1.62.1Compare Source
v1.62.0Compare Source
🧱 New component testing model
Component testing moves to a stories and galleries model.
A story wraps your component in one specific scenario — hard-coded props, mock data, providers — and a
gallery page that you serve renders stories on demand. The new fixtures.mount() fixture navigates
to the gallery, mounts a story by id, and returns a Locator scoped to the story's root element:
Pass a story type as a template argument to type-check its props, and use
update(props)/unmount()on the returned locator to re-render or tear down within a test.🛑 Cancel operations with AbortSignal
Most operations and web-first assertions now accept a
signaloption that takes anAbortSignal, letting youcancel long-running actions, navigations, waits, and assertions:
Providing a signal does not disable the default timeout; pass
timeout: 0to disable it.🖼️ WebP screenshots
expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot()
can now store snapshots in the WebP format — just give the snapshot a
.webpname:page.screenshot() and locator.screenshot() also accept
webpas atype,where quality
100(the default) is lossless and lower values use lossy compression.🧩 Custom test filtering with Reporter.preprocess()
New reporter.preprocess() hook runs after the configuration is resolved and before
reporter.onBegin(), letting a reporter mark individual tests as skipped, excluded,
fixed, or failing through a TestRun object:
🔁 Isolated retries
New testConfig.retryStrategy controls when failed tests are retried. The default
'immediate'retries as soon as a worker is free;'isolated'runs all retries at the end,one by one in a single worker, to minimize interference with the rest of the suite:
New APIs
Browser and Context
credentialsincludes the context's virtual WebAuthn Credentials (passkeys) in the storage state, so they can be persisted and re-seeded into later contexts.Actions
scrolloption ("auto"|"none") on actions to opt out of Playwright's automatic scroll-into-view.Network
Evaluation
Command line & MCP
playwright-cli, runnable vianpx playwright mcpandnpx playwright cli.Reporters
mergeFilesreporter option:Announcements
Browser Versions
This version was also tested against the following stable channels:
apify/actions (apify/actions)
v1.5.0Compare Source
Features
v1.4.1Compare Source
Bug Fixes
astral-sh/setup-uv (astral-sh/setup-uv)
v10.1.0: 🌈 New outputpython-runtime-idand respect NO_PROXYCompare Source
Changes
This release adds more bheind the scene security improvements and also 2 small improvements.
NO_PROXY
This action now respects
no_proxy/NO_PROXYenvironment variables which were previously ignored.New output
python-runtime-idThe new output
python-runtime-idcan be used to know which python version exactly was installed if you useactivate-environment. See pyca/cryptography#15572 (comment) for details on why this can be useful.🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.