Update all minor versions (master) (minor) #11559
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/master-all-minor-versions
branch
5 times, most recently
from
3455f93
to
0dc34bd
Compare
sbrunner
force-pushed
the
renovate/master-all-minor-versions
branch
5 times, most recently
from
4bda994
to
346178b
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -324,7 +324,7 @@ | |||
| @staticmethod | |||
| def __encrypt_password_legacy(password: str) -> str: | |||
| """Hash the given password with SHA1.""" | |||
| return sha1(password.encode("utf8")).hexdigest() # nosec | |||
| return sha1(password.encode("utf8")).hexdigest() # noqa: S324 | |||
Check failure
Code scanning / CodeQL
Use of a broken or weak cryptographic hashing algorithm on sensitive data High
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI about 12 hours ago
To fix the problem, we need to replace the use of the SHA-1 hashing algorithm in the __encrypt_password_legacy method with a more secure algorithm. Since the __encrypt_password method already uses SHA-512, we can update the legacy method to use the same algorithm. This ensures that all password hashing in the system is done using a secure algorithm.
- Replace the SHA-1 hashing algorithm in the
__encrypt_password_legacymethod with SHA-512. - Update the import statements to include the necessary modules for SHA-512 if not already present.
| @@ -325,4 +325,4 @@ | ||
| def __encrypt_password_legacy(password: str) -> str: | ||
| """Hash the given password with SHA1.""" | ||
| return sha1(password.encode("utf8")).hexdigest() # noqa: S324 | ||
| """Hash the given password with SHA-512.""" | ||
| return crypt.crypt(password, crypt.METHOD_SHA512) | ||
|
|
sbrunner
force-pushed
the
renovate/master-all-minor-versions
branch
from
346178b
to
bfa0279
Compare
sbrunner
force-pushed
the
renovate/master-all-minor-versions
branch
5 times, most recently
from
7a74e6f
to
c5e0d9f
Compare
renovate
bot
force-pushed
the
renovate/master-all-minor-versions
branch
from
c5e0d9f
to
5c446f2
Compare
Edited/Blocked NotificationRenovate 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. |
From the artifact of the previous workflow run
| @@ -254,7 +214,7 @@ | |||
| resp = requests.get( | |||
| self.project["checker_url"], | |||
| headers=self.project.get("checker_headers"), | |||
| verify=False, # nosec | |||
| verify=False, # noqa: S501 | |||
Check failure
Code scanning / SonarCloud
Server certificates should be verified during SSL/TLS connections High
This PR contains the following updates:
3.1.0->3.2.09.14.0->9.16.08.37.1->8.42.00.15.2->0.16.012.23.1->12.24.01.21->1.2250.4.3->50.6.01.6.0->1.9.01.6.0->1.9.01.9.1->1.14.11.9.1->1.14.123.7.1->23.9.02.5->2.61.80.7->1.81.11.21.0->1.22.075.3.0.20241112->75.6.0.202411265.96.1->5.97.0Release Notes
eslint/eslintrc (@eslint/eslintrc)
v3.2.0Compare Source
Features
eslint/eslint (@eslint/js)
v9.16.0Compare Source
v9.15.0Compare Source
getsentry/sentry-javascript (@sentry/browser)
v8.42.0Compare Source
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptionsin favor ofvueIntegration(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()tracingOptionsinSentry.init()For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()and itstracingOptionsoption to configure tracing options in the Nuxt SDK:Other Changes
web-vitalsto v4.2.4 (#14439)vueIntegration(#14526)Bundle size 📦
v8.41.0Compare Source
Important Changes
meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
Additionally, the SDK requires the implicit
nitropackdependency to satisfy version^2.10.0andofetchto satisfy^1.4.0.It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.
Deprecations
We are deprecating a few APIs which will be removed in the next major.
The following deprecations will potentially affect you:
feat(core): Update & deprecate
undefinedoption handling (#14450)In the next major version we will change how passing
undefinedtotracesSampleRate/tracesSampler/enableTracingwill behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRatekey is present in the options object.In the next major version, this behavior will be changed so that passing
undefined(or rather having atracesSampleRatekey) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefinedbeing passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0instead, which will also enable tracing in v9.The same applies to
tracesSamplerandenableTracing.feat(core): Log warnings when returning
nullinbeforeSendSpan(#14433)Currently, the
beforeSendSpanoption inSentry.init()allows you to drop individual spans from a trace by returningnullfrom the hook.Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.
With the next major version the
beforeSendSpanAPI can only be used to mutate spans, but no longer to drop them.With this release the SDK will warn you if you are using this API to drop spans.
Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.
Additionally, with the next major version, root spans will also be passed to
beforeSendSpan.feat(utils): Deprecate
@sentry/utils(#14431)With the next major version the
@sentry/utilspackage will be merged into the@sentry/corepackage.It is therefore no longer recommended to use the
@sentry/utilspackage.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration'stracingOptionsoption (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()tracingOptionsinSentry.init()vueIntegration()optionstracingOptionsin thevueIntegration()optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptionsin thevueIntegration().The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.exclude(#14486)Currently it is possible to define
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.excludeoptions inSentry.init()to only apply ESM loader hooks to a subset of modules.This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.
Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
To only wrap modules that have instrumentation, it is recommended to instead set
registerEsmLoaderHooks.onlyIncludeInstrumentedModulestotrue.Note that
onlyIncludeInstrumentedModules: truewill become the default behavior in the next major version and theregisterEsmLoaderHookswill no longer accept fine-grained options.The following deprecations will most likely not affect you unless you are building an SDK yourself:
arrayify(#14405)flatten(#14454)urlEncode(#14406)validSeverityLevels(#14407)getNumberOfUrlSegments(#14458)memoBuilder,BAGGAGE_HEADER_NAME, andmakeFifoCache(#14434)addRequestDataToEventandextractRequestData(#14430)Other Changes
sentry-trace,baggageand DSC handling (#14364)openTelemetryInstrumentationsoption (#14484)NEXT_REDIRECTfrom browser (#14440)Work in this release was contributed by @NEKOYASAN and @fmorett. Thank you for your contributions!
Bundle size 📦
v8.40.0Compare Source
Important Changes
feat(angular): Support Angular 19 (#14398)
The
@sentry/angularSDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecatedAPP_INITIALIZERtoken toprovideAppInitializer.In this case, change the Sentry
TraceServiceinitialization inapp.config.ts:feat(core): Deprecate
debugIntegrationandsessionTimingIntegration(#14363)The
debugIntegrationwas deprecated and will be removed in the next major version of the SDK.To log outgoing events, use Hook Options (
beforeSend,beforeSendTransaction, ...).The
sessionTimingIntegrationwas deprecated and will be removed in the next major version of the SDK.To capture session durations alongside events, use Context (
Sentry.setContext()).feat(nestjs): Deprecate
@WithSentryin favor of@SentryExceptionCaptured(#14323)The
@WithSentrydecorator was deprecated. Use@SentryExceptionCapturedinstead. This is a simple renaming and functionality stays identical.feat(nestjs): Deprecate
SentryTracingInterceptor,SentryService,SentryGlobalGenericFilter,SentryGlobalGraphQLFilter(#14371)The
SentryTracingInterceptorwas deprecated. If you are using@sentry/nestjsyou can safely remove any references to theSentryTracingInterceptor. If you are using another package migrate to@sentry/nestjsand remove theSentryTracingInterceptorafterwards.The
SentryServicewas deprecated and its functionality was added toSentry.init. If you are using@sentry/nestjsyou can safely remove any references to theSentryService. If you are using another package migrate to@sentry/nestjsand remove theSentryServiceafterwards.The
SentryGlobalGenericFilterwas deprecated. Use theSentryGlobalFilterinstead which is a drop-in replacement.The
SentryGlobalGraphQLFilterwas deprecated. Use theSentryGlobalFilterinstead which is a drop-in replacement.feat(node): Deprecate
nestIntegrationandsetupNestErrorHandlerin favor of using@sentry/nestjs(#14374)The
nestIntegrationandsetupNestErrorHandlerfunctions from@sentry/nodewere deprecated and will be removed in the next major version of the SDK. If you're using@sentry/nodein a NestJS application, we recommend switching to our new dedicated@sentry/nestjspackage.Other Changes
normalizedRequestonsdkProcessingMetadatais merged (#14315)@sentry/utilsinto@sentry/core(#14382)__selfand__sourceattributes on feedback nodes (#14356)Bundle size 📦
v8.39.0Compare Source
Important Changes
The
@sentry/nestjsSDK will now capture performance data for NestJS Events (@nestjs/event-emitter)Other Changes
@SentryExceptionCapturedfor@WithSentry(#14322)SentryServicebehaviour into@sentry/nestjsSDKinit()(#14321)SentryGlobalFilter(#14320)childProcessIntegrationforprocessThreadBreadcrumbIntegrationand deprecate it (#14334)_sentryModuleMetadatais not mangled (#14344)sentry.sourceattribute tocustomwhen callingspan.updateNameonSentrySpan(#14251)Requesttype in favor ofRequestEventData(#14317)transactioninrequestDataIntegration(#14306)Bundle size 📦
v8.38.0Compare Source
knexintegration (#13526)tediousintegration (#13486)debug_metawith ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
geoalchemy/geoalchemy2 (GeoAlchemy2)
v0.16.0Compare Source
Azure/azure-sdk-for-python (azure-storage-blob)
v12.24.0Compare Source
12.24.0 (2024-11-13)
Features Added
gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)
v50.6.0Compare Source
Features
checkBlockStartsoption (#1341) (f9b102d)v50.5.0Compare Source
Features
sbrunner/prospector-profile-duplicated (prospector-profile-duplicated)
v1.9.0Compare Source
1.9.0 (2024-12-03)
New feature
61fec84Use Ruff instead of multiple tools (@sbrunner)v1.8.1Compare Source
1.8.1 (2024-12-03)
New feature
Dependency update
v1.8.0Compare Source
1.8.0 (2024-11-15)
New feature
6c28c94Add more rules dupplicated with PyLint (@sbrunner)v1.7.0Compare Source
1.7.0 (2024-11-14)
New feature
Dependency update
sbrunner/prospector-profile-utils (prospector-profile-utils)
v1.14.1Compare Source
1.14.1 (2024-12-03)
New feature
v1.14.0Compare Source
1.14.0 (2024-12-03)
New feature
v1.13.0Compare Source
1.13.0 (2024-12-02)
Fixed bugs
Dependency update
v1.12.2Compare Source
1.12.2 (2024-11-18)
New feature
v1.11.1Compare Source
1.11.1 (2024-11-14)
Fixed bugs
v1.11.0Compare Source
1.11.0 (2024-11-14)
Fixed bugs
Configuration
📅 Schedule: Branch creation - "after 5pm on the first day of the month" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.