Skip to content

Release: Merge release into master from: release/2.57.3#14760

Merged
rossops merged 15 commits intomasterfrom
release/2.57.3
Apr 27, 2026
Merged

Release: Merge release into master from: release/2.57.3#14760
rossops merged 15 commits intomasterfrom
release/2.57.3

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Release triggered by rossops

DefectDojo release bot and others added 15 commits April 20, 2026 15:26
….58.0-dev

Release: Merge back 2.57.2 into bugfix from: master-into-bugfix/2.57.2-2.58.0-dev
Bumps [lxml](https://github.com/lxml/lxml) from 6.0.2 to 6.1.0.
- [Release notes](https://github.com/lxml/lxml/releases)
- [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt)
- [Commits](lxml/lxml@lxml-6.0.2...lxml-6.1.0)

---
updated-dependencies:
- dependency-name: lxml
  dependency-version: 6.1.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Adds user-facing release notes for the 2.57.1 (Apr 13, 2026) and 2.57.2
(Apr 20, 2026) Pro releases, covering Pro UI, Risk Acceptance, Risk SLA,
Surveys, Universal Parser, API, Permissions, Reports, Deduplication,
Rules Engine, Import, and Tools updates.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: global component deduplication

* cleanup
* updated contrast parser and added new unittests and scan files

* Fix path assertion in test to be environment-independent

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Use unique_id_from_tool directly as dupe_key in Contrast parser

No need to SHA256-hash a string that is already a usable dict key.
Aligns with the dominant pattern across parsers that use the tool's
native ID directly rather than computing a hash of it.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…4731)

* Dispatch create-path notifications async to fix slow POST latency

POST /api/v2/engagements/ takes ~5s on large tenants because
create_notification runs recipient enumeration and per-user Alert
writes on the request thread. Move the outer create_notification to a
Celery worker for the five create-path events (engagement_added,
product_added, product_type_added, finding_added, test_added) by
adding async_create_notification (accepts ids, re-fetches, delegates)
and dispatching via dojo_dispatch_task. This extends the existing
per-user async pattern (Slack/email/MSTeams/webhooks) up one level so
the recipient query and Alert fan-out no longer block the response.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Fix ruff D213 and skip dispatch during fixture loads

- Reformat async_create_notification importer-guard docstring to D213 style
- Skip post_save dispatch when raw=True (loaddata) so the k8s initializer's
  fixture install path doesn't require an available Celery broker. Without
  this guard the unconditional async dispatch tries to enqueue during
  product_type.json load and fails with kombu OperationalError.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* optimize async_create_notification to avoid redundant DB fetches

When test_id + engagement_id + product_id are all passed, the original
implementation fetched each object independently (3 queries). Since
Test.select_related("engagement__product") already loads all three in
one query, derive engagement and product from the test instead.

Same for engagement_id + product_id: one query instead of two.

Also updates the no_async performance test expected counts accordingly.

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: valentijnscholten <valentijnscholten@gmail.com>
Bumps [gitpython](https://github.com/gitpython-developers/GitPython) from 3.1.46 to 3.1.47.
- [Release notes](https://github.com/gitpython-developers/GitPython/releases)
- [Changelog](https://github.com/gitpython-developers/GitPython/blob/main/CHANGES)
- [Commits](gitpython-developers/GitPython@3.1.46...3.1.47)

---
updated-dependencies:
- dependency-name: gitpython
  dependency-version: 3.1.47
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>
…14747)

* add ddorch notes

* update

* Apply suggestions from code review

Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>

---------

Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>
@github-actions github-actions Bot requested a review from Maffooch as a code owner April 27, 2026 15:04
@github-actions github-actions Bot added the release-management Automated release-train PR label Apr 27, 2026
@github-actions github-actions Bot requested a review from mtesauro as a code owner April 27, 2026 15:04
@github-actions github-actions Bot added the release-management Automated release-train PR label Apr 27, 2026
@dryrunsecurity
Copy link
Copy Markdown

dryrunsecurity Bot commented Apr 27, 2026

DryRun Security

This pull request modifies a sensitive file (dojo/metrics/views.py), triggering a configured-codepaths warning about sensitive edits; sensitive file paths and allowed authors can be set in .dryrunsecurity.yaml. The finding is flagged as an error (risk_threshold: failing) but marked non-blocking.

🔴 Configured Codepaths Edit in dojo/metrics/views.py (drs_a5b7f8e5)
Vulnerability Configured Codepaths Edit
Description Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

We've notified @mtesauro.


Comment to provide feedback on these findings.

Report false positive: @dryrunsecurity fp [FINDING ID] [FEEDBACK]
Report low-impact: @dryrunsecurity nit [FINDING ID] [FEEDBACK]

Example: @dryrunsecurity fp drs_90eda195 This code is not user-facing

All finding details can be found in the DryRun Security Dashboard.

@rossops rossops closed this Apr 27, 2026
@rossops rossops reopened this Apr 27, 2026
@github-actions github-actions Bot added settings_changes Needs changes to settings.py based on changes in settings.dist.py included in this PR apiv2 docs unittests ui parser helm labels Apr 27, 2026
@rossops rossops merged commit 1d8a9a1 into master Apr 27, 2026
157 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

apiv2 docs helm parser release-management Automated release-train PR settings_changes Needs changes to settings.py based on changes in settings.dist.py included in this PR ui unittests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants