Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update all non-major dependencies #194

Merged
merged 2 commits into from
May 20, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) ^11.11.3 -> ^11.11.4 age adoption passing confidence
@emotion/styled (source) ^11.11.0 -> ^11.11.5 age adoption passing confidence
@generouted/react-router ^1.18.2 -> ^1.19.4 age adoption passing confidence
@mdx-js/rollup (source) ^3.0.0 -> ^3.0.1 age adoption passing confidence
@playwright/test (source) ^1.41.1 -> ^1.44.0 age adoption passing confidence
@swc/core (source) ^1.3.107 -> ^1.5.7 age adoption passing confidence
@swc/plugin-styled-components ^1.5.115 -> ^1.5.122 age adoption passing confidence
@types/react (source) ^18.2.48 -> ^18.3.2 age adoption passing confidence
@types/react-dom (source) ^18.2.18 -> ^18.3.0 age adoption passing confidence
esbuild ^0.20.0 -> ^0.21.3 age adoption passing confidence
picocolors ^1.0.0 -> ^1.0.1 age adoption passing confidence
pnpm (source) 8.15.1 -> 8.15.8 age adoption passing confidence
react (source) ^18.2.0 -> ^18.3.1 age adoption passing confidence
react-dom (source) ^18.2.0 -> ^18.3.1 age adoption passing confidence
react-is (source) ^18.2.0 -> ^18.3.1 age adoption passing confidence
react-router-dom (source) ^6.21.3 -> ^6.23.1 age adoption passing confidence
styled-components (source) ^6.1.8 -> ^6.1.11 age adoption passing confidence
typescript (source) ^5.3.3 -> ^5.4.5 age adoption passing confidence
vite (source) ^5.0.12 -> ^5.2.11 age adoption passing confidence

Release Notes

emotion-js/emotion (@​emotion/react)

v11.11.4

Compare Source

Patch Changes
  • #​3159 5b82631d Thanks @​iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).
oedotme/generouted (@​generouted/react-router)

v1.19.4

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.3...v1.19.4

v1.19.3

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.2...v1.19.3

v1.19.2

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.1...v1.19.2

v1.19.1

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.0...v1.19.1

v1.19.0

Compare Source

Breaking Changes 🚨

Modals export is now removed from the following integrations:

  • @generouted/react-router
  • @generouted/react-router/lazy
  • @generouted/solid-router
  • @generouted/solid-router/lazy
<Modals /> component is now included internally within the <Routes /> component by default

This export was usually used at the highest available layout route src/pages/_app.tsx (as it requires the router context) but it was causing initialization/circular errors as the _app.tsx file is imported by the file that exports Modals component. This is reproducible by triggering HMR updates when _app.tsx is modified. Also in some cases it cause kind of infinite revalidation triggered by this error.

-import { Modals } from '@&#8203;generouted/react-router'
-import { Modals } from '@&#8203;generouted/react-router/lazy'
-import { Modals } from '@&#8203;generouted/solid-router'
-import { Modals } from '@&#8203;generouted/solid-router/lazy'

export default function App() {
  return (
    <section>
      <main>...</main>

-      <Modals />
    </section>
  )
}

Commits

Changelog: oedotme/generouted@v1.18.8...v1.19.0

v1.18.8

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.7...v1.18.8

v1.18.7

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.6...v1.18.7

v1.18.6

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.5...v1.18.6

v1.18.5

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.4...v1.18.5

v1.18.4

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.3...v1.18.4

v1.18.3

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.2...v1.18.3

mdx-js/mdx (@​mdx-js/rollup)

v3.0.1

Compare Source

Fix
Types
Site

Full Changelog: mdx-js/mdx@3.0.0...3.0.1

microsoft/playwright (@​playwright/test)

v1.44.0

Compare Source

New APIs

Accessibility assertions

  • expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

    const locator = page.getByRole('button');
    await expect(locator).toHaveAccessibleName('Submit');
  • expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

    const locator = page.getByRole('button');
    await expect(locator).toHaveAccessibleDescription('Upload a photo');
  • expect(locator).toHaveRole() checks if the element has the specified ARIA role:

    const locator = page.getByTestId('save-button');
    await expect(locator).toHaveRole('button');

Locator handler

  • After executing the handler added with page.addLocatorHandler(), 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() to specify maximum number of times the handler should be run.
  • The handler in page.addLocatorHandler() now accepts the locator as argument.
  • New page.removeLocatorHandler() method for removing previously added locator handlers.
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 option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

    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 or per project in testProject.expect.

  • expect(page).toHaveURL(url) now supports ignoreCase option.

  • testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

  • New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
  • Blob 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 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:

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

    $ 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 124

v1.43.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30300 - [REGRESSION]: UI mode restarts if keep storage statehttps://github.com/microsoft/playwright/issues/303399 - [REGRESSION]: Brand new install of playwright, unable to run chromium with show browser using vscode

Browser Versions
  • Chromium 124.0.6367.29
  • Mozilla Firefox 124.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 123
  • Microsoft Edge 123

v1.43.0

Compare Source

New APIs

  • Method browserContext.clearCookies() now supports filters to remove only some cookies.

    // Clear all cookies.
    await context.clearCookies();
    // New: clear cookies with a particular name.
    await context.clearCookies({ name: 'session-id' });
    // New: clear cookies for a particular domain.
    await context.clearCookies({ domain: 'my-origin.com' });
  • New mode retain-on-first-failure for testOptions.trace. In this mode, trace is recorded for the first run of each test, but not for retires. When test run fails, the trace file is retained, otherwise it is removed.

    import { defineConfig } from '@&#8203;playwright/test';
    
    export default defineConfig({
      use: {
        trace: 'retain-on-first-failure',
      },
    });
  • New property testInfo.tags exposes test tags during test execution.

    test('example', async ({ page }) => {
      console.log(test.info().tags);
    });
  • New method locator.contentFrame() converts a Locator object to a FrameLocator. This can be useful when you have a Locator object obtained somewhere, and later on would like to interact with the content inside the frame.

    const locator = page.locator('iframe[name="embedded"]');
    // ...
    const frameLocator = locator.contentFrame();
    await frameLocator.getByRole('button').click();
  • New method frameLocator.owner() converts a FrameLocator object to a Locator. This can be useful when you have a FrameLocator object obtained somewhere, and later on would like to interact with the iframe element.

    const frameLocator = page.frameLocator('iframe[name="embedded"]');
    // ...
    const locator = frameLocator.owner();
    await expect(locator).toBeVisible();

UI Mode Updates

Playwright UI Mode

  • See tags in the test list.
  • Filter by tags by typing @fast or clicking on the tag itself.
  • New shortcuts:
    • F5 to run tests.
    • Shift F5 to stop running tests.
    • Ctrl ` to toggle test output.

Browser Versions

  • Chromium 124.0.6367.29
  • Mozilla Firefox 124.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 123
  • Microsoft Edge 123

v1.42.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29732 - [Regression]: HEAD requests to webServer.url since v1.42.0https://github.com/microsoft/playwright/issues/297466 - [Regression]: Playwright CT CLI scripts fail due to broken initializePlugin imporhttps://github.com/microsoft/playwright/issues/2973939 - [Bug]: Component tests fails when imported a module with a dot in a nahttps://github.com/microsoft/playwright/issues/29731731 - [Regression]: 1.42.0 breaks some import statemehttps://github.com/microsoft/playwright/issues/297609760 - [Bug]: Possible regression with chained locators in v1.42

Browser Versions
  • Chromium 123.0.6312.4
  • Mozilla Firefox 123.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 122
  • Microsoft Edge 123

v1.42.0

Compare Source

New APIs

  • Test tags

    New tag syntax for adding tags to the tests (@​-tokens in the test title are still supported).

    test('test customer login', { tag: ['@&#8203;fast', '@&#8203;login'] }, async ({ page }) => {
      // ...
    });

    Use --grep command line option to run only tests with certain tags.

    npx playwright test --grep @&#8203;fast
  • Annotating skipped tests

    New annotation syntax for test annotations allows annotating the tests that do not run.

    test('test full report', {
      annotation: [
        { type: 'issue', description: 'https://github.com/microsoft/playwright/issues/23180' },
        { type: 'docs', description: 'https://playwright.dev/docs/test-annotations#tag-tests' },
      ],
    }, async ({ page }) => {
      // ...
    });
  • page.addLocatorHandler()

    New method page.addLocatorHandler() registers a callback that will be invoked when specified element becomes visible and may block Playwright actions. The callback can get rid of the overlay. Here is an example that closes a cookie dialog when it appears.

    // Setup the handler.
    await page.addLocatorHandler(
        page.getByRole('heading', { name: 'Hej! You are in control of your cookies.' }),
        async () => {
          await page.getByRole('button', { name: 'Accept all' }).click();
        });
    // Write the test as usual.
    await page.goto('https://www.ikea.com/');
    await page.getByRole('link', { name: 'Collection of blue and white' }).click();
    await expect(page.getByRole('heading', { name: 'Light and easy' })).toBeVisible();
  • Project wildcard filter
    Playwright command line flag now supports '*' wildcard when filtering by project.

    npx playwright test --project='*mobile*'
  • Other APIs

    • expect(callback).toPass({ timeout })
      The timeout can now be configured by expect.toPass.timeout option globally or in project config

    • electronApplication.on('console')
      electronApplication.on('console') event is emitted when Electron main process calls console API methods.

      electronApp.on('console', async msg => {
        const values = [];
        for (const arg of msg.args())
          values.push(await arg.jsonValue());
        console.log(...values);
      });
      await electronApp.evaluate(() => console.log('hello', 5, { foo: 'bar' }));
    • page.pdf() accepts two new options tagged and outline.

Breaking changes

Mixing the test instances in the same suite is no longer supported. Allowing it was an oversight as it makes reasoning about the semantics unnecessarily hard.

const test = baseTest.extend({ item: async ({}, use) => {} });
baseTest.describe('Admin user', () => {
  test('1', async ({ page, item }) => {});
  test('2', async ({ page, item }) => {});
});

Announcements

  • ⚠️ Ubuntu 18 is not supported anymore.

Browser Versions

  • Chromium 123.0.6312.4
  • Mozilla Firefox 123.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 122
  • Microsoft Edge 123

v1.41.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29123 - [REGRESSION] route.continue: Protocol error (Fetch.continueRequest): Invalid InterceptionId.

Browser Versions

  • Chromium 121.0.6167.57
  • Mozilla Firefox 121.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 120
  • Microsoft Edge 120
swc-project/swc (@​swc/core)

v1.5.7

Compare Source

Documentation

v1.5.6

Compare Source

Bug Fixes

v1.5.5

Compare Source

Bug Fixes
Refactor

v1.5.3

Compare Source

v1.5.2

Compare Source

v1.5.1

Compare Source

Bug Fixes
  • (es/decorator) Support for legacy decorators in class expressions (#​8892) (8fe57ad)

  • (es/helpers) Remove unused export from _using_ctx.js (#​8891) (438d0b3)

  • (es/minifier) Do not add vars if eval exists (#​8888) (be359fa)

v1.5.0

Compare Source

Bug Fixes
Features

v1.4.17

Compare Source

Bug Fixes

v1.4.16

Compare Source

Bug Fixes

v1.4.15

Compare Source

Bug Fixes
Features
Refactor
Build

v1.4.14

Compare Source

Bug Fixes
Documentation
  • (swc_core) Resolve build issue with --all-features flag (#​8848) (c0d901e)
Refactor
Testing

v1.4.13

Compare Source

Bug Fixes

v1.4.12

Compare Source

Bug Fixes
Features
  • (es/minifier) Evaluate spread of arrays (#​8811) (47714c5)

  • (plugin/runner) Improve error message for Wasm plugin crashes ([#​8794](https:/


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 5, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 4616b5d to 5476bcd Compare February 9, 2024 13:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from e1a8add to 6662578 Compare February 19, 2024 06:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a9ab8e3 to 6bfd19c Compare February 24, 2024 15:20
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Feb 26, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from ab04906 to ed14f5b Compare February 27, 2024 21:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 415fa79 to 9a348b4 Compare May 2, 2024 09:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from d56cae7 to ee05fe6 Compare May 12, 2024 22:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 2f840f9 to cebcd45 Compare May 20, 2024 09:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cebcd45 to 6d39933 Compare May 20, 2024 09:37
Copy link
Contributor Author

renovate bot commented May 20, 2024

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.

@ArnaudBarre ArnaudBarre merged commit 59efc9b into main May 20, 2024
1 check passed
@ArnaudBarre ArnaudBarre deleted the renovate/all-minor-patch branch May 20, 2024 09:52
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant