Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 22, 2025
Merged

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

merged 1 commit into from
Jul 22, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 18, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@sentry/node (source) 9.39.0 -> 9.40.0 age confidence
@sentry/react (source) 9.39.0 -> 9.40.0 age confidence
@sentry/vite-plugin (source) 3.6.0 -> 3.6.1 age confidence
@types/node (source) 22.16.3 -> 22.16.5 age confidence
@vitejs/plugin-react (source) 4.6.0 -> 4.7.0 age confidence
cypress (source) 14.5.1 -> 14.5.2 age confidence
eslint-config-prettier 10.1.5 -> 10.1.8 age confidence
eslint-plugin-prettier 5.5.1 -> 5.5.3 age confidence
react-router-dom (source) 7.6.3 -> 7.7.0 age confidence

Release Notes

getsentry/sentry-javascript (@​sentry/node)

v9.40.0

Compare Source

Important Changes
  • feat(browser): Add debugId sync APIs between web worker and main thread (#​16981)

This release adds two Browser SDK APIs to let the main thread know about debugIds of worker files:

  • webWorkerIntegration({worker}) to be used in the main thread
  • registerWebWorker({self}) to be used in the web worker
// main.js
Sentry.init({...})

const worker = new MyWorker(...);

Sentry.addIntegration(Sentry.webWorkerIntegration({ worker }));

worker.addEventListener('message', e => {...});
// worker.js
Sentry.registerWebWorker({ self });

self.postMessage(...);
  • feat(core): Deprecate logger in favor of debug (#​17040)

The internal SDK logger export from @sentry/core has been deprecated in favor of the debug export. debug only exposes log, warn, and error methods but is otherwise identical to logger. Note that this deprecation does not affect the logger export from other packages (like @sentry/browser or @sentry/node) which is used for Sentry Logging.

import { logger, debug } from '@​sentry/core';

// before
logger.info('This is an info message');

// after
debug.log('This is an info message');
  • feat(node): Add OpenAI integration (#​17022)

This release adds official support for instrumenting OpenAI SDK calls in with Sentry tracing, following OpenTelemetry semantic conventions for Generative AI. It instruments:

  • client.chat.completions.create() - For chat-based completions
  • client.responses.create() - For the responses API
// The integration respects your `sendDefaultPii` option, but you can override the behavior in the integration options

Sentry.init({
  dsn: '__DSN__',
  integrations: [
    Sentry.openAIIntegration({
      recordInputs: true, // Force recording prompts
      recordOutputs: true, // Force recording responses
    }),
  ],
});
Other Changes
  • feat(node-core): Expand @opentelemetry/instrumentation range to cover 0.203.0 (#​17043)
  • fix(cloudflare): Ensure errors get captured from durable objects (#​16838)
  • fix(sveltekit): Ensure server errors from streamed responses are sent (#​17044)

Work in this release was contributed by @​0xbad0c0d3 and @​tommy-gilligan. Thank you for your contributions!

Bundle size 📦

Path Size
@​sentry/browser 23.23 KB
@​sentry/browser - with treeshaking flags 21.82 KB
@​sentry/browser (incl. Tracing) 38.73 KB
@​sentry/browser (incl. Tracing, Replay) 75.96 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 80.56 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 92.37 KB
@​sentry/browser (incl. Feedback) 39.53 KB
@​sentry/browser (incl. sendFeedback) 27.8 KB
@​sentry/browser (incl. FeedbackAsync) 32.58 KB
@​sentry/react 24.94 KB
@​sentry/react (incl. Tracing) 40.64 KB
@​sentry/vue 27.57 KB
@​sentry/vue (incl. Tracing) 40.48 KB
@​sentry/svelte 23.25 KB
CDN Bundle 24.59 KB
CDN Bundle (incl. Tracing) 38.49 KB
CDN Bundle (incl. Tracing, Replay) 73.65 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 78.99 KB
CDN Bundle - uncompressed 71.72 KB
CDN Bundle (incl. Tracing) - uncompressed 114.12 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 225.58 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.1 KB
@​sentry/nextjs (client) 42.64 KB
@​sentry/sveltekit (client) 39.14 KB
@​sentry/node 165.02 KB
@​sentry/node - without tracing 97.85 KB
@​sentry/aws-serverless 125.35 KB
getsentry/sentry-javascript-bundler-plugins (@​sentry/vite-plugin)

v3.6.1

Compare Source

  • fix(core): Observe and handle Sentry CLI sourcemap upload failures (#​763)
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.7.0

Compare Source

Add HMR support for compound components (#​518)

HMR now works for compound components like this:

const Root = () => <div>Accordion Root</div>
const Item = () => <div>Accordion Item</div>

export const Accordion = { Root, Item }
Return Plugin[] instead of PluginOption[] (#​537)

The return type has changed from react(): PluginOption[] to more specialized type react(): Plugin[]. This allows for type-safe manipulation of plugins, for example:

// previously this causes type errors
react({ babel: { plugins: ['babel-plugin-react-compiler'] } })
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))
cypress-io/cypress (cypress)

v14.5.2

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#14-5-2

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.8

Compare Source

eslint-config-prettier

10.1.5

Patch Changes

10.1.4

Patch Changes

10.1.3

Patch Changes

10.1.2

Patch Changes

10.1.1

Patch Changes

  • #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

    For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

    See also #​308

    // before
import eslintConfigPrettier from "eslint-config-prettier";

// after
import eslintConfigPrettier from "eslint-config-prettier/flat";

10.1.0

Minor Changes

10.0.3

Patch Changes

10.0.2

Patch Changes

10.0.0

Major Changes

Versions before 10.0.0

Version 9.1.0 (2023-12-02)
Version 9.0.0 (2023-08-05)
  • Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the ESLINT_USE_FLAT_CONFIG environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
  • Changed: unicode-bom is no longer turned off. Prettier preserves the BOM if you have one, and does not add one if missing. It was wrong of eslint-config-prettier to disable that rule. If you get ESLint errors after upgrading, either add "unicode-bom": "off" to your config to disable it again, or run ESLint with --fix to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@​nstepien)!
Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)

  • Changed: All configs have been merged into one!

    To upgrade, change:

    {
  "extends": [
    "some-other-config-you-use",
    "prettier",
    "prettier/@&#8203;typescript-eslint",
    "prettier/babel",
    "prettier/flowtype",
    "prettier/react",
    "prettier/standard",
    "prettier/unicorn",
    "prettier/vue"
  ]
}

    Into:

    {
  "extends": [
    "some-other-config-you-use",
    "prettier"
  ]
}

    The "prettier" config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!

    So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@​lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@​thorn0) for pointing this out!

    If you use eslint-plugin-prettier, all you need is plugin:prettier/recommended:

    {
  "extends": [
    "some-other-config-you-use",
    "plugin:prettier/recommended"
  ]
}

    (The "prettier/prettier" config still exists separately. It’s the odd one out. The main "prettier" config does not include the rules from it.)

  • Changed: The CLI helper tool now only prints warnings for arrow-body-style and prefer-arrow-callback, just like other “special rules.” This means that if you’ve decided to use those rules and eslint-plugin-prettier at the same time, you’ll get warnings but exit code zero (success).

Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)

  • Changed: At least ESLint 7.0.0 is now required.

  • Changed: arrow-body-style and prefer-arrow-callback are no longer turned off by default. They only need to be turned off if you use eslint-plugin-prettier. If you do, add "prettier/prettier" to your "extends" array to turn them off again.

    {
  "extends": ["prettier", "prettier/prettier"],
  "plugins": ["prettier"],
  "rules": {
    "prettier/prettier": "error"
  }
}

    Alternatively, update eslint-plugin-prettier to version 3.2.0 or later which automatically turns off these two rules in its "plugin:prettier/recommended" config.

    The CLI helper tool only warns about these rules if you have the "prettier/prettier" rule enabled for a file.

  • Changed: no-tabs is now a validatable rule. If you use it, you should enable allowIndentationTabs so that the rule works regardless of your Prettier config:

    {
  "rules": {
    "no-tabs": ["error", { "allowIndentationTabs": true }]
  }
}

  • Changed: The CLI helper tool is now called just eslint-config-prettier instead of eslint-config-prettier-check. This is so that npx eslint-config-prettier always works regardless of whether you have already installed eslint-config-prettier or not: If you have, the local installation is used; if you haven’t, npx downloads a temporary copy.

  • Changed: The CLI helper tool no longer requires you to pipe the output of eslint --print-config to it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.

    Before:

    npx eslint --print-config index.js | npx eslint-config-prettier-check

    After:

    npx eslint-config-prettier index.js

  • Improved: The npm package is now 75% smaller.

Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
  • Improved: Recommend using npx when running the CLI helper tool.
  • Updated: Mention that eslint-config-prettier has been tested with Prettier 2.0 and the latest versions of plugins.
Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)

  • Changed: The CLI helper tool now considers no-confusing-arrow to conflict if you use the default value of its allowParens option. The default was changed to true in ESLint 6, which conflicts with Prettier.

    If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:

    {
  "rules": {
    "no-confusing-arrow": ["error"]
  }
}

    Into this:

    {
  "rules": {
    "no-confusing-arrow": ["error", { "allowParens": false }]
  }
}

    The latter works in both ESLint 6 as well as in ESLint 5 and older.

  • Improved: eslint --print-config usage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead of eslint --print-config ., use eslint --print-config path/to/main.js.)

Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)

  • Removed: react/self-closing-comp. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 Prettier stopped converting empty elements to self-closing elements. So the rule is not unnecessary anymore.

    If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.

    If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing <div></div> into <div />. You have two options:

    • Run eslint --fix if you prefer to enforce self-closing elements where possible. This should fix all the errors.
    • Add "react/self-closing-comp": "off" to your ESLint config if you use autofix from your editor and you face the same issue as Prettier did.

  • Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.

Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Version 4.0.0 (2019-01-26)
  • Breaking change: Support for eslint-plugin-typescript has been removed and replaced with support for its successor @​typescript-eslint/eslint-plugin. Thanks to TANIGUCHI Masaya (@​ta2gch) and everyone else who helped with this!
  • Changed: arrow-body-style and prefer-arrow-callback are now marked as special rules, since they might cause problems if using eslint-plugin-prettier and --fix. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.
Version 3.6.0 (2019-01-19)
Version 3.5.0 (2019-01-16)
  • Fixed: The eslint-plugin-vue change from 3.4.0 has been reverted. That change requires eslint-plugin-vue@5, while many use eslint-plugin-vue@4. In other words, it was an accidental breaking change. Also, after thinking about it some more, it makes sense to have a Prettier-specific list of rules, rather than using the vue/no-layout-rules list, since there can be layout rules that don’t conflict with but rather complement Prettier.
  • Added: New eslint-plugin-vue rules coming in the next version after 5.1.0.
Version 3.4.0 (2019-01-13)
  • Added: Support for eslint-plugin-typescript. Thanks to Jed Fox (@​j-f1)!
  • Improved: The eslint-plugin-vue integration is now using the vue/no-layout-rules config behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@​michalsnik)!
Version 3.3.0 (2018-11-11)
Version 3.2.0 (2018-11-10)
  • Added: Support for eslint-plugin-vue.
  • Fixed: The CLI helper tool should now work in Node.js 6 with npm 3 again. Thanks to Grant Snodgrass (@​meeber)!
  • Improved: Updated documentation.
Version 3.1.0 (2018-09-22)
Version 3.0.1 (2018-08-13)
  • Improved: eslint --print-config usage instructions.
Version 3.0.0 (2018-08-13)
  • Breaking change: Dropped Node.js 4 support.
Version 2.10.0 (2018-08-13)
Version 2.9.0 (2017-11-26)
Version 2.8.0 (2017-11-19)
Version 2.7.0 (2017-11-01)
Version 2.6.0 (2017-09-23)
Version 2.5.0 (2017-09-16)
Version 2.4.0 (2017-09-02)
Version 2.3.0 (2017-06-30)
Version 2.2.0 (2017-06-17)
Version 2.1.1 (2017-05-20)
  • No code changes. Just updates to the readme.
Version 2.1.0 (2017-05-13)
Version 2.0.0 (2017-05-07)

  • Changed/Improved: The CLI helper tool is now more helpful.

    • The options of special rules are now validated if possible. If a special rule is enabled with non-conflicting options, the CLI no longer warns about it.
    • If only special rules that cannot be automatically checked are found, the CLI no longer exists with a non-zero exit code. Instead, it only warns about the rules.

  • Changed: The no-confusing-arrow is now a special rule again, since it might conflict with recent Prettier versions.

  • Removed: The react/wrap-multilines rule (which has been deprecated for a while), since it was removed in eslint-plugin-react@7.

Version 1.7.0 (2017-04-19)
  • Changed: The no-confusing-arrow is no longer a special rule, but simply turned off, since recent Prettier versions make it redundant.
  • Improved: The CLI helper tool now has a more helpful message for special rules, and exits with a different status code if only special rules were found. The exit codes are now documented as well.
Version 1.6.0 (2017-04-05)
Version 1.5.0 (2017-03-04)
Version 1.4.1 (2017-02-28)
  • Improved: eslint-config-prettier is now part of the prettier organization! This version updates all URLs to point to the new home of the project.
Version 1.4.0 (2017-02-26)
Version 1.3.0 (2017-02-21)
Version 1.2.0 (2017-02-14)
Version 1.1.1 (2017-02-12)
  • Minor documentation tweak: Changed "Exceptions" into "Special rules".
Version 1.1.0 (2017-02-10)
  • Fixed: The eslint-plugin-react exclusion rules now actually work.
  • Fixed: The CLI helper tool now works in Node.js 4. Thanks to Nathan Friedly (@​nfriedly)!
  • Added: Support for eslint-plugin-flowtype.
  • Improved: Minor things for the CLI helper tool.
  • Improved: There are now tests for everything.
Version 1.0.3 (2017-02-03)
  • Fixed: "extends": "prettier/react" now actually works.
Version 1.0.2 (2017-01-30)
  • Improved: CLI helper tool instructions.
Version 1.0.1 (2017-01-29)
  • No difference from 1.0.0. Just an npm publish mistake.
Version 1.0.0 (2017-01-29)
  • Initial release.
prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.5.3

Compare Source

republish the latest version

Full Changelog: prettier/eslint-plugin-prettier@v5.5.2...v5.5.3

v5.5.2

Compare Source

Changelog

5.5.1

Patch Changes

5.5.0

Minor Changes

5.4.1

Patch Changes
  • #​740 c21521f Thanks @​JounQin! - fix(deps): bump synckit to v0.11.7 to fix potential TypeError: Cannot read properties of undefined (reading 'message') error

5.4.0

Minor Changes

5.3.1

Patch Changes

5.3.0

Minor Changes

5.2.6

Patch Changes

5.2.5

Patch Changes

5.2.4

Patch Changes

5.2.3

Patch Changes

5.2.2

Patch Changes

5.2.1

Patch Changes

5.2.0

Minor Changes

5.1.3

Patch Changes

5.1.2

Patch Changes

  • #​623 8210e44 Thanks @​BPScott! - Add exports mapping to package.json, to allow import eslintPluginRecommended from 'eslint-plugin-prettier/recommended' to work as expected.

    Strictly speaking this is a breaking change as it removes the ability for people to import from "eslint-plugin-prettier/eslint-plugin-prettier.js" and "eslint-plugin-prettier/recommended.js" but the former was never recommended in the first place and the latter has only been available for a few days.

  • #​621 2b09e7f Thanks @​JounQin! - feat: support parsing markdown via eslint-mdx natively

    What means the following is unnecessary anymore when using with eslint-mdx/eslint-plugin-mdx!

    [
  {
    files: ["**/*.md"],
    rules: { "prettier/prettier": ["error", { parser: "markdown" }] },
  },
  {
    files: ["**/*.mdx"],
    rules: { "prettier/prettier": ["error", { parser: "mdx" }] },
  },
]

5.1.1

Patch Changes

5.1.0

Minor Changes

  • #​616 3856413 Thanks @​BPScott! - Add recommended config for the flat config format.

    If you are using flat config, import the recommended config from eslint-plugin-prettier/recommended. Like the legacy format recommended config, this automatically includes the contents of eslint-config-prettier.

    // eslint.config.js
const eslintPluginPrettierRecommended = require("eslint-plugin-prettier/recommended");

module.exports = [
  // Any other config imports go at the top
  eslintPluginPrettierRecommended,
];
Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

n3rdc4ptn
n3rdc4ptn previously approved these changes Jul 18, 2025
View reviewed changes
@n3rdc4ptn
Copy link
Member

We should wait before merging this, until the other PRs are merged (important the Sentry one)

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 819bb40 to fc21604 Compare July 18, 2025 22:09
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v22.16.4 chore(deps): update all non-major dependencies Jul 18, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fc21604 to 418e5b0 Compare July 19, 2025 20:43
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Jul 19, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 53d2821 to c4197b1 Compare July 21, 2025 23:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c4197b1 to a6844b9 Compare July 22, 2025 03:53
@n3rdc4ptn n3rdc4ptn merged commit 5194025 into main Jul 22, 2025
6 checks passed
@n3rdc4ptn n3rdc4ptn deleted the renovate/all-minor-patch branch July 22, 2025 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@n3rdc4ptn n3rdc4ptn n3rdc4ptn approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@n3rdc4ptn