Skip to content

chore(deps): update devdependencies (non-major) - #86

Merged
ganapativs merged 2 commits into
mainfrom
renovate/devdependencies-(non-major)
Jul 29, 2026
Merged

chore(deps): update devdependencies (non-major)#86
ganapativs merged 2 commits into
mainfrom
renovate/devdependencies-(non-major)

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@argos-ci/playwright (source) ^7.3.7^7.4.0 age confidence
@playwright/test (source) ^1.61.1^1.62.0 age confidence
@size-limit/preset-small-lib ^13.0.1^13.0.2 age confidence
@types/node (source) ^26.1.1^26.1.2 age confidence
ai (source) ^7.0.37^7.0.41 age confidence
oxfmt (source) ^0.60.0^0.61.0 age confidence
oxlint (source) ^1.75.0^1.76.0 age confidence
playwright (source) ^1.61.1^1.62.0 age confidence
postcss (source) ^8.5.23^8.5.25 age confidence
size-limit ^13.0.1^13.0.2 age confidence
wrangler (source) ^4.114.0^4.115.0 age confidence

Release Notes

argos-ci/argos-javascript (@​argos-ci/playwright)

v7.4.0

Compare Source

Features
  • expose a baseName option to set fallback baselines (ab26668)
  • playwright: warn when recommended Chromium launch options are missing (a8f6c55)

7.3.7 (2026-07-23)

Note: Version bump only for package @​argos-ci/playwright

7.3.6 (2026-07-12)

Note: Version bump only for package @​argos-ci/playwright

7.3.5 (2026-07-10)

Note: Version bump only for package @​argos-ci/playwright

7.3.4 (2026-07-09)

Note: Version bump only for package @​argos-ci/playwright

7.3.3 (2026-07-09)

Note: Version bump only for package @​argos-ci/playwright

7.3.2 (2026-07-09)

Note: Version bump only for package @​argos-ci/playwright

7.3.1 (2026-07-09)

Note: Version bump only for package @​argos-ci/playwright

microsoft/playwright (@​playwright/test)

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
ai/size-limit (@​size-limit/preset-small-lib)

v13.0.2

Compare Source

  • Fixed glob pattern regression.
vercel/ai (ai)

v7.0.41

Compare Source

Patch Changes
  • 2e2224b: Route the warning system information banner to stderr so it does not corrupt application output written to stdout.
  • Updated dependencies [bf216b3]

v7.0.40

Compare Source

Patch Changes
  • c3782a6: Deprecate Experimental_GeneratedImage in favor of GeneratedFile.

v7.0.39

Compare Source

Patch Changes

v7.0.38

Compare Source

Patch Changes
oxc-project/oxc (oxfmt)

v0.61.0

Compare Source

oxc-project/oxc (oxlint)

v1.76.0

Compare Source

🚀 Features
  • 8d31dfa linter: Verify eslint/no-restricted-globals config schema (#​24598) (vigneshwar)
  • 7069621 linter: Verify jest/vitest prefer-lowercase-title config schema (#​24724) (Bartok)
  • 016cf2a linter/oxc: Add bad-match-all-arg rule (#​24900) (camc314)
  • cdc941e linter/n: Implement exports-style rule (#​24087) (Mikhail Baev)
  • 1ad6f6c linter/eslint: Implement id-denylist rule (#​24632) (Mikhail Baev)
📚 Documentation
postcss/postcss (postcss)

v8.5.25

Compare Source

  • Fixed 8.5.17 visitor regression.
  • Fixed list.split() for non-string values (by @​amir-rezaei).

v8.5.24

Compare Source

  • Preserve the BOM after the processing (by @​hdimer).
cloudflare/workers-sdk (wrangler)

v4.115.0

Compare Source

Minor Changes
  • #​14807 4dfb96e Thanks @​oOPa! - Add hidden --jurisdiction option to wrangler kv namespace create for internal testing

    This option creates a KV namespace within a specific jurisdiction (for example us, eu, or fedramp), backing it with jurisdiction-scoped storage. It is experimental and currently gated to allow-listed accounts, so it is hidden from --help until the feature is generally available.

  • #​14280 465c0fb Thanks @​tahmid-23! - Add experimental local_dev.experimental_s3_credentials to r2_buckets config

    When set, the R2 bucket is served over a local S3-compatible API at /cdn-cgi/local/r2/s3/<bucket-id> during local development, authenticated with the configured AWS SigV4 credentials. <bucket-id> is the bucket's bucket_name, or the binding name if bucket_name is not set:

    {
      "r2_buckets": [
        {
          "binding": "BUCKET",
          "bucket_name": "my-bucket",
          "local_dev": {
            "experimental_s3_credentials": {
              "accessKeyId": "local-access-key-id",
              "secretAccessKey": "local-secret-access-key"
            }
          }
        }
      ]
    }
  • #​14877 552bcfc Thanks @​jasoncabot! - Respect and surface the Retry-After header on Cloudflare API responses

    Previously, if a Wrangler command (e.g. wrangler versions upload, wrangler deploy) hit the Cloudflare API's rate limit, the resulting error gave no indication of how long to wait before trying again, and 429 responses weren't retried at all (only 5xx errors were, with a fixed linear backoff).

    Now:

    • 429 Too Many Requests responses are automatically retried, alongside the existing 5xx retry behaviour.
    • If a retried response includes a Retry-After header, Wrangler waits for that duration instead of the default backoff, and logs a message indicating how long it's waiting. To avoid blocking for an excessive amount of time, waits longer than 60 seconds fail fast instead — the surfaced Retry-After value lets the caller schedule its own retry.
    • If a retryable error is ultimately surfaced to the user (e.g. because retries were exhausted), the error message includes a note with the Retry-After duration, and the command-failed entry written to the Wrangler output file (WRANGLER_OUTPUT_FILE_PATH/WRANGLER_OUTPUT_FILE_DIRECTORY) gains a retry_after_ms field. This lets scripts and CI/CD pipelines calling Wrangler repeatedly (for example, wrangler versions upload on every commit) read the wait duration directly instead of regex-parsing stderr.

    APIError.isRetryable() is unchanged (still 5xx only); retryOnAPIFailure() separately retries 429s. retryAfterMs, when present, is honoured for any retried error, not just 429s.

    retryAfterMs is also now populated on APIErrors raised from direct R2 object requests, the Browser Rendering API, and errors surfaced from commands using the official cloudflare SDK client.

  • #​14712 6e0bf6e Thanks @​mack-erel! - Support connect() on remote VPC Network and VPC Service bindings in local development

    Remote VPC Network and VPC Service bindings previously only supported HTTP and JSRPC, so calling binding.connect(address) against a private TCP service (for example a database) failed in local dev with Incoming CONNECT on a worker not supported. Raw TCP connections through remote VPC Network and VPC Service bindings now work in local development.

    This feature is experimental. Existing HTTP and JSRPC usage of remote VPC Network and VPC Service bindings is unaffected, and no new configuration is required.

Patch Changes
  • #​14833 773ead4 Thanks @​DiogoSantoss! - Color Email Routing plan change markers

    Wrangler now highlights additions in green, updates in yellow, and deletions and conflicts in red so Email Routing deployment plans are easier to scan before confirmation.

  • #​14833 773ead4 Thanks @​DiogoSantoss! - Apply Email Routing changes across independent zones concurrently

    Wrangler now limits concurrent zone updates while preserving the Email Routing plan order within each zone. Deployments that configure addresses across multiple zones complete faster without breaking delete-before-add transitions at a zone's rule limit.

  • #​14815 09b8a44 Thanks @​chinesepowered! - Fix wrangler cloudchamber curl mangling header values that contain a colon

    Header values were split on every colon and only the segment between the first and second was sent, so --header location:https://example.com/x arrived as https. Headers are now split on the first colon only. A header that is not in the documented --header <name>:<value> form previously threw an unhandled TypeError, and now reports a clear error.

  • #​14806 e8b3a9d Thanks @​akim136! - Handle and explain authentication failures from remote bindings during local development

    Wrangler now recognizes authentication failures from remote preview sessions and reports that bindings which need to run remotely require Cloudflare authentication even when the rest of the Worker is developed locally.

  • #​14801 b737676 Thanks @​emily-shen! - Speed up old debug log cleanup by reading each log file's date from its filename instead of stat-ing every file

    Wrangler periodically deletes debug log files older than 30 days from its logs directory. Previously it made a filesystem stat call for each file to read its modification time; it now derives the age from the timestamp already encoded in the log filename, avoiding that extra work.

  • Updated dependencies [1035f74, e426cb9, 3a22ae5, 465c0fb, 6e0bf6e]:

    • miniflare@​4.20260722.1

Configuration

📅 Schedule: (in timezone Asia/Kolkata)

  • Branch creation
    • "before 9am on monday"
  • 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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 27, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
microcharts d5223b6 Commit Preview URL

Branch Preview URL
Jul 29 2026, 05:43 PM

@renovate
renovate Bot force-pushed the renovate/devdependencies-(non-major) branch 10 times, most recently from 24be335 to 2008565 Compare July 29, 2026 16:54
@github-actions

Copy link
Copy Markdown
Contributor

📦 Bundle size — no change

Every measured subpath is byte-identical to origin/main.

@renovate
renovate Bot force-pushed the renovate/devdependencies-(non-major) branch from 2008565 to 397c01b Compare July 29, 2026 16:56
The grouped bump swept playwright 1.61.1 -> 1.62.0 along with it, and
every test-browser leg died: `test-browser` and `visual` run inside
mcr.microsoft.com/playwright:v1.61.1-noble, which ships the browsers
preinstalled, so a package newer than the tag finds no executable at
/ms-playwright/. MCR has not published a v1.62.0 image yet, so the tag
cannot follow.

Both entries are now exact rather than caret. A caret is the wrong
shape for this constraint: ^1.61.1 resolves straight back to 1.62.0,
which is how the drift happened in the first place. The version has to
equal the image tag, so it is written as one version.

The lockfile is re-resolved from main rather than hand-edited —
@axe-core/playwright had otherwise kept a stale playwright-core@1.62.0
peer while the root dependency sat at 1.61.1.

The other nine updates in this group are untouched.
@ganapativs

Copy link
Copy Markdown
Owner

Pushed a fix so this can land: playwright is held at 1.61.1 and the other nine updates in the group are untouched.

test-browser and visual run inside mcr.microsoft.com/playwright:v1.61.1-noble, which ships the browsers preinstalled. The npm package and that tag are one version, so bumping the package alone left every leg with no executable at /ms-playwright/. MCR has not published a v1.62.0 image yet (tag list tops out at 1.61.1), so the tag cannot follow right now.

Two details worth noting:

  • Both entries are now exact, not caret. ^1.61.1 resolves straight back to 1.62.0, which is how the drift happened — the constraint is "equals the image tag", so it is written as one version.
  • The lockfile is re-resolved from main rather than hand-edited. @axe-core/playwright had otherwise kept a stale playwright-core@1.62.0 peer while the root dependency sat at 1.61.1.

#93 adds the Renovate rule that stops this recurring: playwright moves to its own group behind dependencyDashboardApproval, so the next bump waits for someone who can check the tag list and edit ci.yml + visual.yml in the same PR.

Local gate green before push: gen:check, typecheck, 896 node tests, docs tests, browser tests.

@renovate

renovate Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@ganapativs
ganapativs merged commit 88af809 into main Jul 29, 2026
10 checks passed
@ganapativs
ganapativs deleted the renovate/devdependencies-(non-major) branch July 29, 2026 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant