fix(deps): update all non-major dependencies#203
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
3a521f4 to
b0fbbae
Compare
b0fbbae to
b9af16a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^10.53.1→^10.56.0^4.1.7→^4.1.8v6.0.2→v6.0.3^0.51.0→^0.53.0^1.66.0→^1.68.010.33.4→10.34.1^5.0.0→^5.1.0^19.13.0→^19.14.1^0.22.0→^0.22.1^4.1.7→^4.1.8Release Notes
getsentry/sentry-javascript (@sentry/node)
v10.56.0Compare Source
Important Changes
feat(deno): Redis diagnostics channel based integration for Deno (#21087)
Adds Redis integration support for Deno, covering both
redisandioredisclients.Other Changes
@sentry/nodewas imported instead of@sentry/hono/node(#21240)consistentTraceSamplingis enabled (#21281)instrumentDurableObjectWithSentrybreaking Cloudflare Agents (#21101)WeakReffor Span-Scope circular references (#21242)InstrumentationNodeModuleFileto fix Bun--bytecodecrash (#21262)Internal Changes
hrTimeutilities from@opentelemetry/core(#21191)http.route(#21193)TraceStateimplementation (#21192)dataCollection(#21282)Bundle size 📦
v10.55.0Compare Source
Important Changes
feat(hono): Promote
@sentry/honoto stable and deprecatehonoIntegration(#21208)The
@sentry/honoSDK is now stable. See the Sentry Hono SDK docs to get started.docs(tanstackstart-react): Promote SDK status to beta (#21175)
This release promotes the
@sentry/tanstackstart-reactSDK to beta. For details on how to use it, check out theSentry TanStack Start SDK docs. Please reach out on
GitHub if you have any feedback or concerns.
feat(hono): Add
shouldHandleErroroption tosentry()middleware (#21205)The
sentry()middleware now accepts ashouldHandleErrorcallback to control which errors are captured and sent to Sentry. By default, 3xx/4xx HTTP errors are ignored and 5xx errors and plainErrorobjects are captured. Returntruefrom the callback to capture an error,falseto suppress it.test(tanstackstart-react): Move initialization to client entry point (#21161)
Change the recommended setup for the SDK to do
Sentry.init()in the client entry file to capture telemetry that is emitted ahead of page hydration.feat(tanstackstart-react): Add distributed tracing (#21144)
Server and client traces are now automatically connected, allowing you to see the full request lifecycle from server-side rendering through client-side hydration in a single trace.
feat(tanstackstart-react): Add server-side route parametrization (#21147)
Server transaction names are now parametrized automatically (e.g.,
GET /users/123becomesGET /users/$userId), improving transaction grouping in Sentry.feat(tanstackstart-react): Show readable server function names in traces (#21190)
Server function spans now show human-readable names (e.g.,
GET /_serverFn/greetinstead ofGET /_serverFn/a10e70b3...). Thetanstackstart.function.hash.sha256span attribute has been renamed totanstackstart.function.id.Other Changes
dataCollection(#21071)dataCollectioninstead ofsendDefaultPii(#21078)Elysiaapp type to support Elysia options (#21164)Internal Changes
beforeSend*callbacks (#21186)astro-6e2e test build by relaxing astro version range (#21211)normalizecode out of core (#21172)registerSpanErrorInstrumentation()on server (#21169)v10.54.0Compare Source
Important Changes
feat(core): Support array attributes for spans, logs, and metrics (#20427)
Arrays of primitive values (
string,number,boolean) are now accepted as attribute values. Arrays containing non-primitive elements will be dropped and won't show up in Sentry. Array attributes on logs and metrics were previously stringified and will now be sent as actual arrays instead. If you have custom rules that process attribute values in anybeforeSend*callbacks (e.g., data scrubbing), you may need to update them to correctly handle array values.For instance, here's how you can update a
beforeSendLogcallback to handle arrays:feat(browser): Add
fetchStreamPerformanceIntegrationfor streamed response tracking (#20778)A new integration that tracks the performance of streamed fetch responses. Use this to measure time-to-first-byte and streaming duration for APIs that return chunked/streamed data. This replaces the now deprecated
trackFetchStreamPerformanceoption.feat(core): Add
dataCollectionclient option (#20965)Adds a new
dataCollectionclient option for controlling what data the SDK collects and sends to Sentry. This provides a centralized way to configure data collection behavior across different SDK features. In the future, this option will be used for fine-granular data filtering, while the simplesendDefaultPiiboolean option will be deprecated and removed in a future release.feat(hono): Add
hono.requestspans for internal.request()calls (#20843)The Hono SDK now creates spans for internal
.request()calls, providing better visibility into request handling within Hono applications.Other Changes
sentry.sdk.integrationson streamed segment spans (#20428)dataCollection(#21080)dataCollection(#21085)dataCollection(#21072)node:httpon versions that support it (#21009)browserTracingIntegration(#20702)dataCollection(#21073)<head>inside attribute values (#21089)attachStacktraceis true (#19988)Deno.serveinstrumentation on Deno 2.8 (#21155)projectoption type tostring | string[](#21067)http.clientdouble-wrap message (#20705)sentry.replay_idattribute on streamed spans (#20897)replay_idon DSC after buffer-to-session conversion (#20686)types-hoisttotypes(#20979)Internal Changes
sendDefaultPii(#20967)@opentelemetry/instrumentation-httpdependency (#21113)@fastify/otel(#21099)@opentelemetry/instrumentation-pg(#21102)@opentelemetry/sql-common(#21140)@prisma/instrumentation(#21098)Work in this release was contributed by @abcang, @ahmadio, @delorge, @mdnanocom, and @victorgarciaesgi. Thank you for your contributions!
vitest-dev/vitest (@vitest/coverage-v8)
v4.1.8Compare Source
🐞 Bug Fixes
cdpAPI whenallowWrite/allowExec: false[backport to v4] - by @hi-ogawa and Codex in #10450 (e4067)View changes on GitHub
actions/checkout (actions/checkout)
v6.0.3Compare Source
oxc-project/oxc (oxfmt)
v0.53.0Compare Source
v0.52.0Compare Source
🚀 Features
16b8058oxfmt: Supportvite-plus/resolveConfigfor vite.config.ts (#22454) (leaysgur)oxc-project/oxc (oxlint)
v1.68.0Compare Source
🚀 Features
e4b1f46linter/typescript: Implementmethod-signature-stylerule (#22679) (Mikhail Baev)bc462calinter/vue: Implement no-reserved-component-names rule (#22741) (bab)ef9e751linter/vue: Implement component-definition-name-casing rule (#22818) (bab)d67f51alinter/vue: Implement require-prop-type-constructor rule (#22708) (bab)8422e8blinter/jsdoc: Implementrequire-yields-descriptionrule (#22805) (Mikhail Baev)fe93f97linter/eslint: Implementprefer-named-capture-grouprule (#22759) (Sebastian Poxhofer)v1.67.0Compare Source
🚀 Features
b84941elinter/vue: Implement no-expose-after-await rule (#22675) (bab)98b98c1linter/vue: Implement no-computed-properties-in-data rule (#22674) (bab)2d4c919oxlint: Supportvite-plus/resolveConfigfor vite.config.ts (#22456) (leaysgur)2a60012linter/vue: Implement require-render-return rule (#22613) (bab)9f227fdlinter/vue: Implement no-deprecated-props-default-this rule (#21892) (bab)87f065elinter/vue: Implement return-in-emits-validator rule (#21935) (bab)ea0380clinter/unicorn: Implementimport-stylerule (#22173) (Hao Chen)dde40felinter/vue: Implement no-watch-after-await rule (#22006) (bab)a735eb0linter/vue: Implement valid-next-tick rule (#22531) (bab)6dc615dlinter/vue: Implement no-shared-component-data rule (#21842) (bab)a656418linter/vue: Implement valid-define-options rule (#22107) (bab)bb6f1b2linter/vue: Implement require-slots-as-functions rule (#22244) (bab)5fa4774linter/n: Implementcallback-returnrule (#22470) (Mikhail Baev)pnpm/pnpm (pnpm)
v10.34.1: pnpm 10.34.1Compare Source
Patch Changes
pnpm-lock.yamlentries whose remote tarballresolution:block is missing theintegrityfield. Previously the worker that extracts a downloaded tarball skipped hash verification when no integrity was supplied and minted a fresh one from the unverified bytes, so an attacker who could both alter the lockfile (e.g. via a pull request that stripsintegrity:) and serve modified content at the referenced tarball URL could install a tampered package without any error — including under--frozen-lockfile. pnpm now fails closed at lockfile-read time withERR_PNPM_MISSING_TARBALL_INTEGRITY. Git-hosted tarballs (gitHosted: trueor a URL on codeload.github.com / bitbucket.org / gitlab.com) andfile:tarballs are exempt — the commit SHA in a git-host URL and the user-controlled local path already anchor the bytes.Platinum Sponsors
Gold Sponsors
v10.34.0: pnpm 10.34Compare Source
Minor Changes
Treat tarball-integrity mismatches against the lockfile as a hard failure by default. Previously,
pnpm install(non-frozen) would logERR_PNPM_TARBALL_INTEGRITY, silently re-resolve from the registry, and overwrite the locked integrity — which meant a compromised registry, proxy, or republished version could substitute attacker-controlled content on a clean machine even though the project shipped a committed lockfile.pnpm installnow exits withERR_PNPM_TARBALL_INTEGRITYand a hint pointing at the new opt-in flag.The only opt-in is
pnpm install --update-checksums— narrowly scoped to refreshing the locked integrity values from what the registry currently serves. Mirrors yarn's flag of the same name. A warning still prints when the bypass takes effect so the operation is auditable.--forceandpnpm updatedeliberately do not bypass the integrity check. They are routine refresh operations; silently overwriting a locked integrity in those flows would erase the protection a committed lockfile is supposed to provide.--frozen-lockfilebehavior is unchanged.--fix-lockfilekeeps its documented purpose (filling in missing lockfile entries) and is also not a bypass.Patch Changes
_authToken,_auth,username/_password,tokenHelper, inlinecert/key) to the registry declared in the same config source at load time, so a later layer overridingregistry=(workspace.npmrc,pnpm-workspace.yaml, CLI--registry) cannot redirect a credential or client certificate authored for a different host. A deprecation warning is emitted whenever an unscoped per-registry setting is encountered, naming the source and the URL it was pinned to. Reported by JUNYI LIU.minimumReleaseAgehandling when cached metadata is abbreviated. The npm registry returns abbreviated package metadata (without the per-versiontimefield) by default, which made the maturity check throwERR_PNPM_MISSING_TIMEwhenever cached abbreviated metadata was reused. pnpm now upgrades cached abbreviated metadata to the full document via a follow-up fetch whenminimumReleaseAgeis active, persists the upgrade to the on-disk cache so subsequent installs skip the extra fetch, and letsERR_PNPM_MISSING_TIMEfrom the cache fast-path fall through to the network fetch even under strict mode.commitfield is not a 40-character hexadecimal SHA before invokinggit. A malicious lockfile could otherwise smuggle a value such as--upload-pack=<command>throughgit fetch/git checkout, which on SSH or local-file transports executes the supplied command.diff --githeaders reference paths outside the patched package directory. Previously a malicious.patchfile added via a pull request could write, delete, or rename arbitrary files reachable by the user runningpnpm install.--prefix=<dir>not being honored when locating the workspace root. The--prefix → dirrename was applied after workspace detection, so workspace settings declared in<dir>/pnpm-workspace.yamlwere not loaded when pnpm was invoked from outside<dir>#11535.@x/../../../../../.git/hooks) when reading them from a package manifest or symlinking them intonode_modules. A malicious registry package could otherwise use a transitive dependency key to makepnpm installcreate symlinks at attacker-chosen paths outside the intendednode_modulesdirectory.Platinum Sponsors
Gold Sponsors
arthurfiorette/prisma-json-types-generator (prisma-json-types-generator)
v5.1.0Compare Source
What's Changed
groupBy/aggregateoperations!Full Changelog: arthurfiorette/prisma-json-types-generator@v5.0.0...v5.1.0
antfu-collective/taze (taze)
v19.14.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v19.14.0Compare Source
🚀 Features
Configuration
📅 Schedule: (UTC)
🚦 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 was generated by Mend Renovate. View the repository job log.