Skip to content

chore(deps): update patch/minor dependencies - #855

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all-non-major
Open

chore(deps): update patch/minor dependencies#855
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all-non-major

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence Type Update
@playwright/test (source) 1.61.11.63.0 age confidence dependencies minor
apify/actions v1.4.0v1.5.0 age confidence action minor
apify/actor-python 3.133.14 age confidence final minor
astral-sh/setup-uv v10.0.1v10.1.0 age confidence action minor
oven/bun 1.31.4 age confidence final minor
playwright (source) 1.61.11.63.0 age confidence dependencies minor
playwright (source) 1.59.11.63.0 age confidence dependencies minor
playwright (source) 1.61.11.63.0 age confidence devDependencies minor

Release Notes

microsoft/playwright (@​playwright/test)

v1.63.0

Compare Source

v1.62.1

Compare Source

v1.62.0

Compare 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:

test('click should expand', async ({ mount }) => {
  const component = await mount('components/Expandable/Stateful');
  await component.getByRole('button').click();
  await expect(component.getByTestId('expanded')).toHaveValue('true');
});

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 signal option that takes an
AbortSignal, letting you
cancel long-running actions, navigations, waits, and assertions:

const controller = new AbortController();
setTimeout(() => controller.abort(), 1000);

await page.getByRole('button', { name: 'Submit' }).click({ signal: controller.signal });
await expect(page.getByText('Done')).toBeVisible({ signal: controller.signal });

Providing a signal does not disable the default timeout; pass timeout: 0 to disable it.

🖼️ WebP screenshots

expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot()
can now store snapshots in the WebP format — just give the snapshot a .webp name:

// Visual comparisons store the golden snapshot as lossless WebP.
await expect(page).toHaveScreenshot('homepage.webp');

// Standalone screenshots can trade quality for size with lossy WebP.
await page.screenshot({ path: 'homepage.webp', quality: 50 });

page.screenshot() and locator.screenshot() also accept webp as a type,
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:

class MyReporter {
  async preprocess({ config, suite, testRun }) {
    for (const test of suite.allTests()) {
      if (shouldSkip(test))
        testRun.skip(test);
    }
  }
}
🔁 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:

// playwright.config.ts
export default defineConfig({
  retries: 2,
  retryStrategy: 'isolated',
});
New APIs
Browser and Context
  • New option credentials includes the context's virtual WebAuthn Credentials (passkeys) in the storage state, so they can be persisted and re-seeded into later contexts.
Actions
  • New scroll option ("auto" | "none") on actions to opt out of Playwright's automatic scroll-into-view.
Network
Evaluation
Command line & MCP
Reporters
  • The HTML report's Merge files grouping — previously only a UI toggle — can now be enabled from the config with the new mergeFiles reporter option:
// playwright.config.ts
export default defineConfig({
  reporter: [['html', { mergeFiles: true }]],
});
Announcements
  • ⚠️ Debian 11 is not supported anymore.
Browser Versions
  • Chromium 151.0.7922.34
  • Mozilla Firefox 153.0
  • WebKit 26.5

This version was also tested against the following stable channels:

  • Google Chrome 151
  • Microsoft Edge 151
apify/actions (apify/actions)

v1.5.0

Compare Source

Features
  • git-cliff-release: Determine pre-release numbers (#​39) (b1c5894)

v1.4.1

Compare Source

Bug Fixes
  • git-cliff-release: upload the generated changelog as an artifact (#​36) (8a3e3b2)
astral-sh/setup-uv (astral-sh/setup-uv)

v10.1.0: 🌈 New output python-runtime-idand respect NO_PROXY

Compare 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_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 (comment) for details on why this can be useful.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from l2ysho as a code owner July 16, 2026 16:23
@renovate
renovate Bot enabled auto-merge (squash) July 16, 2026 16:23
@renovate
renovate Bot requested a review from DaveHanns as a code owner July 16, 2026 16:23
@renovate

renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
[ERROR] This project is configured to use 11.13.0 of pnpm. Your current pnpm is v11.26.0
If you want to bypass this version check, you can set the "pmOnFail" configuration to "warn" or "ignore" (e.g. via --pm-on-fail=ignore). If using "devEngines.packageManager", you can set its "onFail" to "warn" or "ignore"

@renovate
renovate Bot force-pushed the renovate/all-non-major branch 5 times, most recently from a60a9e3 to 8f315cb Compare July 19, 2026 17:04
@l2ysho l2ysho added wontfix Issues that will not be worked on (invalid, outdated, out of scope...). dependencies Pull requests that update a dependency file. labels Jul 20, 2026 — with Claude
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 7 times, most recently from 35efc3b to f465e4f Compare July 25, 2026 22:50
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 8 times, most recently from 3b0ab55 to d31dd63 Compare August 4, 2026 16:36
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 2 times, most recently from 54060fb to 540838b Compare August 7, 2026 00:01
@renovate
renovate Bot force-pushed the renovate/all-non-major branch from 540838b to 032d09a Compare August 10, 2026 16:38
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 4 times, most recently from 6a7842e to 59f3b58 Compare September 1, 2026 14:13
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 3 times, most recently from 4e8deff to c129a21 Compare September 3, 2026 20:32
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
renovate Bot force-pushed the renovate/all-non-major branch 20 times, most recently from 5c1bb27 to 2beb215 Compare September 9, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file. wontfix Issues that will not be worked on (invalid, outdated, out of scope...).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants