Closed renovate[bot] closed 3 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
programming-in-th | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 7, 2024 9:53pm |
Status | Category | Percentage | Covered / Total |
---|---|---|---|
🔵 | Lines | 1.28% | 147 / 11481 |
🔵 | Statements | 1.28% | 147 / 11481 |
🔵 | Functions | 2.25% | 4 / 177 |
🔵 | Branches | 8.94% | 17 / 190 |
This PR contains the following updates:
1.43.1
->1.44.0
15.0.6
->15.0.7
20.12.8
->20.12.10
11.1.7
->11.1.9
9.0.6
->9.1.0
7.51.3
->7.51.4
1.76.0
->1.77.0
3.23.6
->3.23.7
Release Notes
microsoft/playwright (@playwright/test)
### [`v1.44.0`](https://togithub.com/microsoft/playwright/releases/tag/v1.44.0) [Compare Source](https://togithub.com/microsoft/playwright/compare/v1.43.1...v1.44.0) #### New APIs **Accessibility assertions** - [expect(locator).toHaveAccessibleName()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-have-accessible-name) checks if the element has the specified accessible name: ```js const locator = page.getByRole('button'); await expect(locator).toHaveAccessibleName('Submit'); ``` - [expect(locator).toHaveAccessibleDescription()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-have-accessible-description) checks if the element has the specified accessible description: ```js const locator = page.getByRole('button'); await expect(locator).toHaveAccessibleDescription('Upload a photo'); ``` - [expect(locator).toHaveRole()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-have-role) checks if the element has the specified ARIA role: ```js const locator = page.getByTestId('save-button'); await expect(locator).toHaveRole('button'); ``` **Locator handler** - After executing the handler added with [page.addLocatorHandler()](https://playwright.dev/docs/api/class-page#page-add-locator-handler), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new `noWaitAfter` option. - You can use new `times` option in [page.addLocatorHandler()](https://playwright.dev/docs/api/class-page#page-add-locator-handler) to specify maximum number of times the handler should be run. - The handler in [page.addLocatorHandler()](https://playwright.dev/docs/api/class-page#page-add-locator-handler) now accepts the locator as argument. - New [page.removeLocatorHandler()](https://playwright.dev/docs/api/class-page#page-remove-locator-handler) method for removing previously added locator handlers. ```js const locator = page.getByText('This interstitial covers the button'); await page.addLocatorHandler(locator, async overlay => { await overlay.locator('#close').click(); }, { times: 3, noWaitAfter: true }); // Run your tests that can be interrupted by the overlay. // ... await page.removeLocatorHandler(locator); ``` **Miscellaneous options** - [`multipart`](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-fetch-option-multipart) option in `apiRequestContext.fetch()` now accepts [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData) and supports repeating fields with the same name. ```js const formData = new FormData(); formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' })); formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' })); context.request.post('https://example.com/uploadFiles', { multipart: formData }); ``` - `expect(callback).toPass({ intervals })` can now be configured by `expect.toPass.inervals` option globally in [testConfig.expect](https://playwright.dev/docs/api/class-testconfig#test-config-expect) or per project in [testProject.expect](https://playwright.dev/docs/api/class-testproject#test-project-expect). - `expect(page).toHaveURL(url)` now supports `ignoreCase` [option](https://playwright.dev/docs/api/class-pageassertions#page-assertions-to-have-url-option-ignore-case). - [testProject.ignoreSnapshots](https://playwright.dev/docs/api/class-testproject#test-project-ignore-snapshots) allows to configure per project whether to skip screenshot expectations. **Reporter API** - New method [suite.entries()](https://playwright.dev/docs/api/class-suite#suite-entries) returns child test suites and test cases in their declaration order. [suite.type](https://playwright.dev/docs/api/class-suite#suite-type) and [testCase.type](https://playwright.dev/docs/api/class-testcase#test-case-type) can be used to tell apart test cases and suites in the list. - [Blob](https://playwright.dev/docs/test-reporters#blob-reporter) reporter now allows overriding report file path with a single option `outputFile`. The same option can also be specified as `PLAYWRIGHT_BLOB_OUTPUT_FILE` environment variable that might be more convenient on CI/CD. - [JUnit](https://playwright.dev/docs/test-reporters#junit-reporter) reporter now supports `includeProjectInTestName` option. **Command line** - `--last-failed` CLI option for running only tests that failed in the previous run. First run all tests: ```sh $ npx playwright test Running 103 tests using 5 workers ... 2 failed [chromium] › my-test.spec.ts:8:5 › two ───────────────────────────────────────────────────────── [chromium] › my-test.spec.ts:13:5 › three ────────────────────────────────────────────────────── 101 passed (30.0s) ``` Now fix the failing tests and run Playwright again with `--last-failed` option: ```sh $ npx playwright test --last-failed Running 2 tests using 2 workers 2 passed (1.2s) ``` #### Browser Versions - Chromium 125.0.6422.14 - Mozilla Firefox 125.0.1 - WebKit 17.4 This version was also tested against the following stable channels: - Google Chrome 124 - Microsoft Edge 124testing-library/react-testing-library (@testing-library/react)
### [`v15.0.7`](https://togithub.com/testing-library/react-testing-library/compare/v15.0.6...c1f2957a219ec7e6a6159a57c5d0717655c515cd) [Compare Source](https://togithub.com/testing-library/react-testing-library/compare/v15.0.6...v15.0.7)framer/motion (framer-motion)
### [`v11.1.9`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#1119-2024-05-07) [Compare Source](https://togithub.com/framer/motion/compare/v11.1.8...v11.1.9) ##### Changed - Reinstating async event handlers to fix issues with user code and Suspence within Framer. ### [`v11.1.8`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#1118-2024-05-06) [Compare Source](https://togithub.com/framer/motion/compare/v11.1.7...v11.1.8) ##### Fixed - Animating between keyframe unit types when one keyframe is `0` and the other is an explicitly defined keyframe, e.g `y: ["100%", 0]`.pnpm/pnpm (pnpm)
### [`v9.1.0`](https://togithub.com/pnpm/pnpm/compare/v9.1.0-0...v9.1.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.6...v9.1.0)react-hook-form/react-hook-form (react-hook-form)
### [`v7.51.4`](https://togithub.com/react-hook-form/react-hook-form/releases/tag/v7.51.4): Version 7.51.4 [Compare Source](https://togithub.com/react-hook-form/react-hook-form/compare/v7.51.3...v7.51.4) 👹 close [#11778](https://togithub.com/react-hook-form/react-hook-form/issues/11778) improve unregister omit key with getValues method ([#11779](https://togithub.com/react-hook-form/react-hook-form/issues/11779)) 🐞 fix [#11794](https://togithub.com/react-hook-form/react-hook-form/issues/11794) issue: Fields dirty state is not updated when passing values to useFormsass/dart-sass (sass)
### [`v1.77.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1770) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.76.0...1.77.0) - *Don't* throw errors for at-rules in keyframe blocks.colinhacks/zod (zod)
### [`v3.23.7`](https://togithub.com/colinhacks/zod/compare/v3.23.6...f985b5b922cb357dbf4b25bb43814d19f838e046) [Compare Source](https://togithub.com/colinhacks/zod/compare/v3.23.6...v3.23.7)Configuration
📅 Schedule: Branch creation - "before 4am on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.