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 #178

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 12, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) ^7.22.1 -> ^7.22.5 age adoption passing confidence
@babel/plugin-proposal-pipeline-operator (source) ^7.18.9 -> ^7.22.5 age adoption passing confidence
@babel/plugin-transform-react-jsx-self (source) ^7.21.0 -> ^7.22.5 age adoption passing confidence
@babel/plugin-transform-react-jsx-source (source) ^7.19.6 -> ^7.22.5 age adoption passing confidence
@emotion/react (source) ^11.11.0 -> ^11.11.1 age adoption passing confidence
@types/node (source) ^18.16.16 -> ^18.16.17 age adoption passing confidence
@types/react (source) ^18.2.8 -> ^18.2.11 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.59.8 -> ^5.59.9 age adoption passing confidence
@typescript-eslint/parser ^5.59.8 -> ^5.59.9 age adoption passing confidence
playwright-chromium (source) ^1.34.3 -> ^1.35.0 age adoption passing confidence
react-router-dom ^6.11.2 -> ^6.12.1 age adoption passing confidence
rollup (source) ^3.23.1 -> ^3.25.1 age adoption passing confidence
vitest ^0.31.4 -> ^0.32.0 age adoption passing confidence

Release Notes

babel/babel

v7.22.5

Compare Source

🐛 Bug Fix
💅 Polish
emotion-js/emotion

v11.11.1

Compare Source

Patch Changes
  • #​3048 9357f337 Thanks @​naari3! - Added ElementType to the Emotion's JSX namespace. It's defined in the same way as the one in @types/react and should make it possible to use components that return strings, Promises and other types that are valid in React.
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.59.9

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.59.9

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

Microsoft/playwright

v1.35.0

Compare Source

Highlights
  • UI mode is now available in VSCode Playwright extension via a new "Show trace viewer" button:

    Playwright UI Mode

  • UI mode and trace viewer mark network requests handled with page.route() and browserContext.route() handlers, as well as those issued via the API testing:

    Trace Viewer

  • New option maskColor for methods page.screenshot(), locator.screenshot(), expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() to change default masking color:

    await page.goto('https://playwright.dev');
    await expect(page).toHaveScreenshot({
      mask: [page.locator('img')],
      maskColor: '#​00FF00', // green
    });
  • New uninstall CLI command to uninstall browser binaries:

    $ npx playwright uninstall # remove browsers installed by this installation
    $ npx playwright uninstall --all # remove all ever-install Playwright browsers
  • Both UI mode and trace viewer now could be opened in a browser tab:

    $ npx playwright test --ui-port 0 # open UI mode in a tab on a random port
    $ npx playwright show-trace --port 0 # open trace viewer in tab on a random port
⚠️ Breaking changes
  • playwright-core binary got renamed from playwright to playwright-core. So if you use playwright-core CLI, make sure to update the name:

    $ npx playwright-core install # the new way to install browsers when using playwright-core

    This change does not affect @playwright/test and playwright package users.

Browser Versions
  • Chromium 115.0.5790.13
  • Mozilla Firefox 113.0
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 114
  • Microsoft Edge 114
remix-run/react-router

v6.12.1

Compare Source

Patch Changes
  • Adjust feature detection of React.startTransition to fix webpack + react 17 compilation error (#​10569)
  • Updated dependencies:

v6.12.0

Compare Source

Minor Changes
  • Wrap internal router state updates with React.startTransition if it exists (#​10438)
Patch Changes
rollup/rollup

v3.25.1

Compare Source

2023-06-12

Bug Fixes
  • Respect __NO_SIDE_EFFECTS__ for async functions (#​5031)
Pull Requests

v3.25.0

Compare Source

2023-06-11

Features
  • Add this.info and this.debug plugin context logging functions (#​5026)
  • Add onLog option to read, map and filter logs (#​5026)
  • Add logLevel option to fully suppress logs by level (#​5026)
  • Support function logs in this.warn, this.info and this.debug to avoid heavy computations based on log level (#​5026)
  • Add onLog plugin hook to read, filter and map logs from plugins (#​5026)
Pull Requests

v3.24.1

Compare Source

2023-06-10

Bug Fixes
  • Fix an issue where bundles with @rollup/plugin-commonjs were missing internal dependencies when code-splitting (#​5029)
  • Do not use process.exit(0) in watch mode to avoid issues in embedded scenarios (#​5027)
Pull Requests

v3.24.0

Compare Source

2023-06-07

Features
  • Add new annotation /* #__NO_SIDE_EFFECTS__ */ to mark function declarations as side effect free (#​5024)
Pull Requests
  • #​5024: feat: support #__NO_SIDE_EFFECTS__ annotation for function declaration (@​antfu)
vitest-dev/vitest

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

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 force-pushed the renovate/all-minor-patch branch from 4864a74 to d46e828 Compare June 12, 2023 05:01
@ArnaudBarre ArnaudBarre merged commit 0d3d41b into main Jun 12, 2023
8 checks passed
@ArnaudBarre ArnaudBarre deleted the renovate/all-minor-patch branch June 12, 2023 08:04
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.

None yet

1 participant