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.

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

Update all non-major dependencies #2631

Open
wants to merge 1 commit into
base: livekit
Choose a base branch
from
Open

Update all non-major dependencies #2631

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/react (source) 8.28.0 -> 8.30.0 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 8.4.0 -> 8.6.0 age adoption passing confidence
@typescript-eslint/parser (source) 8.4.0 -> 8.6.0 age adoption passing confidence
@vitest/coverage-v8 (source) 2.0.5 -> 2.1.1 age adoption passing confidence
eslint (source) 8.57.0 -> 8.57.1 age adoption passing confidence
eslint-plugin-react 7.35.2 -> 7.36.1 age adoption passing confidence
i18next (source) 23.14.0 -> 23.15.1 age adoption passing confidence
knip (source) 5.30.0 -> 5.30.2 age adoption passing confidence
postcss (source) 8.4.45 -> 8.4.47 age adoption passing confidence
postcss-preset-env (source) 10.0.2 -> 10.0.3 age adoption passing confidence
posthog-js 1.160.3 -> 1.162.0 age adoption passing confidence
react-i18next 15.0.1 -> 15.0.2 age adoption passing confidence
sass 1.78.0 -> 1.79.2 age adoption passing confidence
typescript (source) 5.5.4 -> 5.6.2 age adoption passing confidence
vitest (source) 2.0.5 -> 2.1.1 age adoption passing confidence

Release Notes

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

v8.30.0

Compare Source

Important Changes
  • feat(node): Add kafkajs integration (#​13528)

This release adds a new integration that instruments kafkajs library with spans and traces. This integration is
automatically enabled by default, but can be included with the Sentry.kafkaIntegration() import.

Sentry.init({
  integrations: [Sentry.kafkaIntegration()],
});
Other Changes
  • feat(core): Allow adding measurements without global client (#​13612)
  • feat(deps): Bump @​opentelemetry/instrumentation-undici from 0.5.0 to 0.6.0 (#​13622)
  • feat(deps): Bump @​sentry/cli from 2.33.0 to 2.35.0 (#​13624)
  • feat(node): Use @opentelemetry/instrumentation-undici for fetch tracing (#​13485)
  • feat(nuxt): Add server config to root folder (#​13583)
  • feat(otel): Upgrade @​opentelemetry/semantic-conventions to 1.26.0 (#​13631)
  • fix(browser): check supportedEntryTypes before caling the function (#​13541)
  • fix(browser): Ensure Standalone CLS span timestamps are correct (#​13649)
  • fix(nextjs): Widen removal of 404 transactions (#​13628)
  • fix(node): Remove ambiguity and race conditions when matching local variables to exceptions (#​13501)
  • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#​13640)
  • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#​13642)
  • fix(vue): Ensure Vue trackComponents list matches components with or without <> (#​13543)
  • ref(profiling): Conditionally shim cjs globals (#​13267)

Work in this release was contributed by @​Zen-cronic and @​odanado. Thank you for your contributions!

v8.29.0

Compare Source

Important Changes
  • Beta releases of official Solid and SolidStart Sentry SDKs

This release marks the beta releases of the @sentry/solid and @sentry/solidstart Sentry SDKs. For details on how to
use them, check out the
Sentry Solid SDK README and the
Sentry SolidStart SDK README
respectively. Please reach out on GitHub if you have
any feedback or concerns.

  • feat(node): Option to only wrap instrumented modules (#​13139)

Adds the SDK option to only wrap ES modules with import-in-the-middle that specifically need to be instrumented.

import * as Sentry from '@&#8203;sentry/node';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  registerEsmLoaderHooks: { onlyHookedModules: true },
});
  • feat(node): Update OpenTelemetry packages to instrumentation v0.53.0 (#​13587)

All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8
and fixes various bugs related to ESM mode.

Other Changes
  • feat(nextjs): Emit warning when using turbopack (#​13566)
  • feat(nextjs): Future-proof Next.js config options overriding (#​13586)
  • feat(node): Add generic-pool integration (#​13465)
  • feat(nuxt): Upload sourcemaps generated by Nitro (#​13382)
  • feat(solidstart): Add browserTracingIntegration by default (#​13561)
  • feat(solidstart): Add sentrySolidStartVite plugin to simplify source maps upload (#​13493)
  • feat(vue): Only start UI spans if parent is available (#​13568)
  • fix(cloudflare): Guard context.waitUntil call in request handler (#​13549)
  • fix(gatsby): Fix assets path for sourcemaps upload (#​13592)
  • fix(nextjs): Use posix paths for sourcemap uploads (#​13603)
  • fix(node-fetch): Use stringified origin url (#​13581)
  • fix(node): Replace dashes in generic-pool span origins with underscores (#​13579)
  • fix(replay): Fix types in WebVitalData (#​13573)
  • fix(replay): Improve replay web vital types (#​13602)
  • fix(utils): Keep logger on carrier (#​13570)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

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

v8.6.0

Compare Source

🚀 Features

  • add allow option for restrict-template-expressions

  • type-utils: isNullableType add Void logic

  • eslint-plugin: [no-unnecessary-condition] check switch cases

  • eslint-plugin: [no-misused-promises] check array predicate return

🩹 Fixes

  • eslint-plugin: [no-deprecated] don't report recursive types in destructuring assignment twice

  • eslint-plugin: [no-deprecated] report on deprecated variables used in destructuring assignment

  • eslint-plugin: [no-deprecated] report on deprecated properties with function-like types

  • eslint-plugin: [no-unnecessary-condition] properly reflect multiple negations in message

❤️ Thank You
  • Abraham Guo
  • auvred
  • Josh Goldberg ✨
  • Kim Sang Du
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v8.5.0

Compare Source

🚀 Features

  • eslint-plugin: [no-duplicate-type-constituents] prevent unnecessary `

  • eslint-plugin: [no-unsafe-argument] differentiate error types

🩹 Fixes

  • eslint-plugin: [no-unnecessary-type-assertion] fix TSNonNullExpression fixer

  • eslint-plugin: [no-misused-promises] handle static method

  • eslint-plugin: [no-unnecessary-type-parameters] fix AST quick path scope analysis

  • eslint-plugin: [consistent-type-assertions] access parser services lazily

❤️ Thank You
  • f44da95
  • Josh Goldberg ✨
  • Kirk Waiblinger
  • YeonJuan

You can read about our versioning strategy and releases on our website.

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

v8.6.0

Compare Source

v8.5.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitest-dev/vitest (@​vitest/coverage-v8)

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
eslint/eslint (eslint)

v8.57.1

Compare Source

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.36.1

Compare Source

Fixed

v7.36.0

Compare Source

Added
Fixed
  • [function-component-definition], [boolean-prop-naming], [jsx-first-prop-new-line], [jsx-props-no-multi-spaces], propTypes: use type args (#​3629 @​HenryBrown0)
  • JSX pragma: fail gracefully (#​3632 @​ljharb)
  • [jsx-props-no-spreading]: add explicitSpread option to schema (#​3799 @​ljharb)
Changed
i18next/i18next (i18next)

v23.15.1

Compare Source

  • types(TFunction): make return not inferrable and use defaultValue as return when provided 2234

v23.15.0

Compare Source

  • support unescaped variables in TypeScript 2233
webpro-nl/knip (knip)

v5.30.2

Compare Source

v5.30.1

Compare Source

  • Support snapshotSerializers in jest config resolver (b69c6a3)
  • Treat --package arg the same as positional arg in npx resolver w/ --yes arg (b41594d)
  • Update configuration.md (#​774) (39d473a)
postcss/postcss (postcss)

v8.4.47

Compare Source

  • Removed debug code.

v8.4.46

Compare Source

  • Fixed Cannot read properties of undefined (reading 'before').
csstools/postcss-plugins (postcss-preset-env)

v10.0.3

Compare Source

September 9, 2024

PostHog/posthog-js (posthog-js)

v1.162.0

Compare Source

  • fix(surveys): 7-point likert scale didn't work with branching logic (#​1424)

v1.161.6

Compare Source

  • fix: when capturing without performance entry we can capture manual initiator type (#​1422)
  • chore: auto publish alpha versions (#​1414)
  • chore: move test file into tests (#​1418)

v1.161.5

Compare Source

  • fix: teardown and restart recording on session id change (#​1411)

v1.161.4

Compare Source

  • fix: no keep alive for large payloads (#​1416)
  • feat(experiments): Apply no-code experiments to the webpage. (#​1409)

v1.161.3

Compare Source

  • fix: manage capture pageview hook lifecycle (#​1408)

v1.161.2

Compare Source

  • fix: some clients need web vitals directly on window (#​1406)

v1.161.1

Compare Source

  • fix: warn on unavailable lazy load not throw (#​1400)

v1.161.0

Compare Source

i18next/react-i18next (react-i18next)

v15.0.2

Compare Source

  • try to fix Trans handling with alwaysFormat set to true 1801
sass/dart-sass (sass)

v1.79.2

Compare Source

  • Add a $space parameter to the suggested replacement for color.red(),
    color.green(), color.blue(), color.hue(), color.saturation(),
    color.lightness(), color.whiteness(), and color.blackness().

  • Update deprecation warnings for the legacy JS API to include a link to
    relevant documentation.

v1.79.1

Compare Source

  • No user-visible changes.

v1.79.0

Compare Source

  • Breaking change: Passing a number with unit % to the $alpha parameter
    of color.change(), color.adjust(), change-color(), and adjust-color()
    is now interpreted as a percentage, instead of ignoring the unit. For example,
    color.change(red, $alpha: 50%) now returns rgb(255 0 0 / 0.5).

  • Potentially breaking compatibility fix: Sass no longer rounds RGB channels
    to the nearest integer. This means that, for example, rgb(0 0 1) != rgb(0 0 0.6). This matches the latest version of the CSS spec and browser behavior.

  • Potentially breaking compatibility fix: Passing large positive or negative
    values to color.adjust() can now cause a color's channels to go outside that
    color's gamut. In most cases this will currently be clipped by the browser and
    end up showing the same color as before, but once browsers implement gamut
    mapping it may produce a different result.

  • Add support for CSS Color Level 4 [color spaces]. Each color value now tracks
    its color space along with the values of each channel in that color space.
    There are two general principles to keep in mind when dealing with new color
    spaces:

    1. With the exception of legacy color spaces (rgb, hsl, and hwb), colors
      will always be emitted in the color space they were defined in unless
      they're explicitly converted.

    2. The color.to-space() function is the only way to convert a color to
      another color space. Some built-in functions may do operations in a
      different color space, but they'll always convert back to the original space
      afterwards.

  • rgb colors can now have non-integer channels and channels outside the normal
    gamut of 0-255. These colors are always emitted using the rgb() syntax so
    that modern browsers that are being displayed on wide-gamut devices can
    display the most accurate color possible.

  • Add support for all the new color syntax defined in Color Level 4, including:

    • oklab(), oklch(), lab(), and lch() functions;
    • a top-level hwb() function that matches the space-separated CSS syntax;
    • and a color() function that supports the srgb, srgb-linear,
      display-p3, a98-rgb, prophoto-rgb, rec2020, xyz, xyz-d50, and
      xyz-d65 color spaces.

  • Add new functions for working with color spaces:

    • color.to-space($color, $space) converts $color to the given $space. In
      most cases this conversion is lossless—the color may end up out-of-gamut for
      the destination color space, but browsers will generally display it as best
      they can regardless. However, the hsl and hwb spaces can't represent
      out-of-gamut colors and so will be clamped.

    • color.channel($color, $channel, $space: null) returns the value of the
      given $channel in $color, after converting it to $space if necessary.
      It should be used instead of the old channel-specific functions such as
      color.red() and color.hue().

    • color.same($color1, $color2) returns whether two colors represent the same
      color even across color spaces. It differs from $color1 == $color2 because
      == never consider colors in different (non-legacy) spaces as equal.

    • color.is-in-gamut($color, $space: null) returns whether $color is
      in-gamut for its color space (or $space if it's passed).

    • color.to-gamut($color, $space: null) returns $color constrained to its
      space's gamut (or to $space's gamut, if passed). This is generally not
      recommended since even older browsers will display out-of-gamut colors as
      best they can, but it may be necessary in some cases.

    • color.space($color): Returns the name of $color's color space.

    • color.is-legacy($color): Returns whether $color is in a legacy color
      space (rgb, hsl, or hwb).

    • color.is-powerless($color, $channel, $space: null): Returns whether the
      given $channel of $color is powerless in $space (or its own color
      space). A channel is "powerless" if its value doesn't affect the way the
      color is displayed, such as hue for a color with 0 chroma.

    • color.is-missing($color, $channel): Returns whether $channel's value is
      missing in $color. Missing channels can be explicitly specified using the
      special value none and can appear automatically when color.to-space()
      returns a color with a powerless channel. Missing channels are usually
      treated as 0, except when interpolating between two colors and in
      color.mix() where they're treated as the same value as the other color.

  • Update existing functions to support color spaces:

    • hsl() and color.hwb() no longer forbid out-of-bounds values. Instead,
      they follow the CSS spec by clamping them to within the allowed range.

    • color.change(), color.adjust(), and color.scale() now support all
      channels of all color spaces. However, if you want to modify a channel
      that's not in

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner September 16, 2024 00:06
toger5
toger5 requested changes Sep 16, 2024
View reviewed changes
Copy link
Contributor

@toger5 toger5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linter is not happy with this. To me it looks like we need to patch th js-sdk for this to be fixed

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 21fa004 to cb1d6e4 Compare September 18, 2024 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@toger5 toger5 toger5 requested changes

Requested changes must be addressed to merge this pull request.

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
@toger5