[dependabot]

Bumps the actions group with 6 updates:

Package	From	To
bencherdev/bencher	0.6.13	0.6.14
astral-sh/setup-uv	10.3.0	10.3.3
docker/login-action	4.6.0	4.7.0
pypa/cibuildwheel	4.3.3	4.3.5
cachix/install-nix-action	31.11.2	31.11.3
SonarSource/sonarqube-scan-action	8.3.0	8.4.0

Updates bencherdev/bencher from 0.6.13 to 0.6.14

Release notes

Sourced from bencherdev/bencher's releases.

v0.6.14

• Add --start-point-idempotency-key (or BENCHER_START_POINT_IDEMPOTENCY_KEY) to bencher run, bencher report create, and bencher branch update, so parallel jobs that reset a Branch with the same key share one Head; in GitHub Actions, bencher run defaults the key to the workflow run attempt
• Fix concurrent runs on a Branch failing when they create the same Thresholds, such as parallel runs that clone Thresholds from a start point; the first run creates them and the rest use them
• Add GET /v0/server/health, which checks that the API server runs and reaches its database
• BREAKING CHANGE Remove GET /v0/projects. List an organization's projects with GET /v0/organizations/{organization}/projects, which bencher project list now calls with a required organization argument, and the MCP list_projects tool now takes an organization and asks an anonymous caller to sign in
• Add --image-cache-size to runner up (or BENCHER_IMAGE_CACHE_SIZE), the bytes of Image config and layer blobs a Bare Metal Runner keeps across Jobs in blobs under its --state-dir, so a Job downloads only the blobs the Runner does not already hold, while its manifest still comes from the registry. Between Jobs the least recently used blobs are removed until the rest fit, a Runner given a size exits at startup if it cannot make the store its own, and without one the Runner keeps none
• A Bare Metal Job whose image cannot be pulled or prepared now fails, even with --allow-failure, instead of completing with no results
• A Bare Metal build time now covers the image's command alone, timed where the command runs, and no longer includes the image pull, unpack, and boot; only an iteration whose command succeeds reports one
• Support Hyperfine 2 JSON output in the shell_hyperfine adapter (Thank you mrazauskas)
• Fix a very large page query parameter returning the wrong page
• BREAKING CHANGE Cap perf queries at 8 branches, testbeds, benchmarks, and measures each, and at 64 permutations and 64 lines; extra entries are ignored rather than refused
• Add a plus_limit server config option for the daily metrics limit of organizations with a Bencher Plus plan
• BREAKING CHANGE Cap a plot at 8 branches, testbeds, benchmarks, and measures each
• Cap active Thresholds at 64 per Branch, Testbed, and Measure, and skip the Thresholds a report cannot create (over a cap or over the daily creation limit) instead of failing the report
• BREAKING CHANGE The plus.litestream server config key is removed; use plus.disaster_recovery. A config that still uses plus.litestream is ignored and disaster recovery does not run at all: no restore at startup and no replication
• BREAKING CHANGE The sftp disaster recovery replica scheme is removed; file and s3 remain
• BREAKING CHANGE The on demand database backup is removed: POST /v0/server/backup, bencher server backup, and the database.data_store server config section
• BREAKING CHANGE The container registry storage config moves from plus.registry.data_store (service: aws_s3, an S3 access point ARN) to plus.registry.storage (scheme: file | s3, a bucket plus optional endpoint, region, and path), and any S3-compatible object store now works. Stored keys and the local directory layout are unchanged for a plain prefix, so existing data is picked up as is; a path that began or ended with a slash is now normalized, and one containing a character the store percent-encodes is now encoded, so see the config reference before upgrading. A config that still carries data_store is ignored and the registry falls back to local files
• BREAKING CHANGE A Bare Metal Runner that executes sandboxed Jobs must now run as root, where before it did not. Confining the Firecracker VMM requires privileges that enabling KVM does not grant: mknod to create the sandbox's /dev/kvm, chown to hand the guest images to the sandbox user, pivot_root, and setns to join an empty network namespace. A world-readable /dev/kvm is enough to use KVM unprivileged but not to build the sandbox around it. Start runner up as root, or as a service that starts it as root. If you cannot run as root, start the Runner with --danger-allow-no-sandbox and assign it only Specs with no Sandbox; be aware that this gives up the microVM itself and not just its confinement, so those Jobs execute directly on the host
• Confine the Firecracker VMM on Bare Metal Runners with the Firecracker jailer: the VMM behind each sandboxed Job now runs in a chroot as a dedicated unprivileged user, in an empty network namespace, and is placed in its cgroup before it starts, so a VMM escape no longer lands as root on the Runner host holding the Runner key and every prior Job's work. The user defaults to 61016 and is settable with --jail-uid/--jail-gid, neither of which may be 0
• Add --state-dir to the Runner (default /var/lib/bencher-runner), a persistent directory holding the chroot each sandboxed Job's VMM runs in. Before every sandboxed Job it is swept of anything a previous Runner left behind, since a Runner killed mid-Job cannot clean up after itself. A host runs one Runner at a time, whatever its state directory: a Runner started as root holds /run/bencher/runner.lock for as long as it runs, and a second one started as root exits at once with an error naming that lock; a Runner that is not root cannot open the lock and runs without it. When a Runner started as root comes up, and again before each sandboxed Job, it kills any process still running in a cgroup under /sys/fs/cgroup/bencher, such as the sandbox of a Runner killed mid-Job, whatever that Runner's state directory
• BREAKING CHANGE Sandboxed Jobs on Bare Metal Runners now need Linux 5.14 or later and a writable cgroup v2 hierarchy on every host, a one-core host included: each sandboxed Job runs in its own cgroup under /sys/fs/cgroup/bencher, with the cpuset, memory, and pids controllers enabled, and the Runner kills a Job's processes, and anything a Runner left there, through that cgroup's cgroup.kill. On an older kernel a Runner exits at startup or, started with --danger-allow-no-sandbox, fails each sandboxed Job
• Write Runner logs to stderr as JSON, and stop relaying a Job's output into runner up's log
• BREAKING CHANGE Remove --grace-period from runner up and runner run, so a Runner started with it now fails to parse its arguments. A sandboxed Job's results now leave the guest on a drive the Runner reads only once the VM has powered off, so there is no grace period left to wait out: each sandboxed Job ends about a second sooner, a guest that powers off without its results fails the Job at once rather than at its timeout, and a guest still running at its timeout has a few more seconds to write its results and power off before it is killed
• BREAKING CHANGE POST /v0/runners/{runner}/specs and bencher runner spec add now return the Runner, with its updated specs, instead of the Spec. Older CLI versions still add the Spec but cannot parse the new response, so update the CLI before using bencher runner spec add
• Show a Runner's last heartbeat and its latest status (taking Jobs or paused, why it is paused, and its disk health) on the admin Runner endpoints and in bencher system runner view
• Email server admins when a Runner's disk health changes or shows a new problem, when a Runner stays paused for more than 12 hours, and when it takes Jobs again
• Pause a Bare Metal Runner between Jobs while an md RAID array on its host resyncs, recovers, checks, repairs, or reshapes: it takes no new Job until the sync is done and never stops a running one. Start runner up with --no-raid-pause to keep taking Jobs
• Have a Bare Metal Runner take turns with host maintenance: it holds /run/bencher/job.lock through each Job, and pauses while another process holds the lock or a marker named /run/bencher/maintenance or /run/bencher/maintenance.<name> exists, so touch /run/bencher/maintenance drains it. runner run waits for the lock too. /run/bencher is now root's alone
• Report a Bare Metal Runner's disk health with each ready and paused: its md arrays at every poll, and its NVMe drives' SMART / health logs at most hourly, which needs root
• Record the project key that creates a Report, which the Report now names in project_key
• Deleting a Project now requires the Maintainer role, which Organization Leaders and server admins hold
• Add --threshold-metric and --threshold-parameters to bencher run and bencher report create to declare the metric and the parameters a Threshold checks
• Add optional metrics, hidden, focus, and layout fields to plots, so a pinned plot keeps the metrics it draws, the lines it hides, the line it focuses, and how it lays out its measures; set them with POST /v0/projects/{project}/plots, and change them, or clear them with null, with PATCH /v0/projects/{project}/plots/{plot}
• Filter the Reports list by adapter and alerts=active, and count each Report iteration's lines
• Cap a project at 64 plots: POST /v0/projects/{project}/plots refuses another with a 400 until one is deleted
• Add --bmf-version to bencher project update, so a server admin can move a Project to BMF version 1
• BREAKING CHANGE Security fix for URL validation: a project URL must now use http or https, an existing project URL that does not is shown as plain text, and the Console no longer links to a URL with any other scheme
• Security fix for the Console's embed snippet: it now escapes the project name and title
• Add Bencher to the Claude connectors directory
• Every Project, at either BMF version, now opens in the new Console at the Console's own paths: the classic Console's Project, Organization, and account pages are removed and their links redirect, and the public projects list is removed, with /perf redirecting to /explore

Commits

• 58a33f7 Release from any branch (#1379)
• 72a8549 Build the GitHub Action with the repo's Node (#1380)
• 987e57f Release v0.6.14
• 2538bc3 Add the Building Bencher in 2026 engineering post (#1352)
• f58c544 Release Bencher from a workflow dispatch (#1348)
• 23d3de2 Tint a run's report rows on the Runs list (#1376)
• 733aafe Read the usage after the plan on Stripe's return (#1368)
• 5900ecf Expand a run in place on the Runs list (#1367)
• 25da67e Ignore RUSTSEC-2026-0387 until jsonwebtoken moves to p256 0.14 (#1359)
• ff79988 Bump the GitHub Action to the ESM @actions packages (#1366)
• Additional commits viewable in compare view

Updates astral-sh/setup-uv from 10.3.0 to 10.3.3

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.3.3 🌈 Use Astral mirror for version manifests with GitHub fallback

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable. (Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes

• Use Astral mirror for version manifests with GitHub fallback @​eifinger (#1119)
• fix: allow whitespace in uv requirement specifiers @​soujasK (#1112)
• fix: resolve ~= specifiers with PEP 440 semantics @​soujasK (#1111)
• fix: only report a saved cache when saving succeeded @​soujasK (#1110)

🧰 Maintenance

• chore: update known checksums for 0.13.6 @github-actions[bot] (#1117)

📚 Documentation

• docs: use JSDoc for compatible release specifier comment @​eifinger (#1113)
• docs: update version references to v10.3.2 @github-actions[bot] (#1104)

v10.3.2 🌈 update known checksums for 0.13.5

Changes

🧰 Maintenance

• chore: update known checksums for 0.13.5 @github-actions[bot] (#1103)

📚 Documentation

• docs: update version references to v10.3.1 @github-actions[bot] (#1102)

v10.3.1 🌈 preserve cache error class names in save-cache bundle

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

• fix: preserve cache error class names in save-cache bundle @​dannyward630 (#1093)

🧰 Maintenance

... (truncated)

Commits

• 68559e9 Use Astral mirror for version manifests with GitHub fallback (#1119)
• 0192b69 chore: update known checksums for 0.13.6 (#1117)
• 2f29784 docs: use JSDoc for compatible release specifier comment (#1113)
• 9c73321 fix: allow whitespace in uv requirement specifiers (#1112)
• 80fbe01 fix: resolve ~= specifiers with PEP 440 semantics (#1111)
• 36b7b57 fix: only report a saved cache when saving succeeded (#1110)
• 56618ca docs: update version references to v10.3.2 (#1104)
• 07a047e chore: update known checksums for 0.13.5 (#1103)
• e1b8536 docs: update version references to v10.3.1 (#1102)
• 18d369b chore(deps): roll up Dependabot updates (#1101)
• Additional commits viewable in compare view

Updates docker/login-action from 4.6.0 to 4.7.0

Release notes

Sourced from docker/login-action's releases.

v4.7.0

• Preserve explicit ECR settings in registry-auth by @​crazy-max in docker/login-action#1089
• Use registry hosts for scoped credentials by @​crazy-max in docker/login-action#1088
• Raise Docker Hub OIDC max expiry to 6 hours by @​crazy-max in docker/login-action#1068
• Log Docker Hub OIDC token exchange progress by @​crazy-max in docker/login-action#1061
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1154.0 in docker/login-action#1093
• Bump @​docker/actions-toolkit from 0.94.0 to 0.107.0 in docker/login-action#1100
• Bump @​humanfs/node from 0.16.7 to 0.16.8 in docker/login-action#1077
• Bump csv-parse from 7.0.1 to 7.0.3 in docker/login-action#1078
• Bump handlebars from 4.7.9 to 4.7.10 in docker/login-action#1091
• Bump js-yaml from 5.2.2 to 5.5.0 in docker/login-action#1066
• Bump postcss from 8.5.22 to 8.5.26 in docker/login-action#1071
• Bump postcss-selector-parser from 7.1.1 to 7.1.6 in docker/login-action#1092
• Bump source-map-js from 1.2.1 to 1.2.2 in docker/login-action#1090
• Bump undici from 6.27.0 to 6.29.1 in docker/login-action#1085
• Bump uuid from 14.0.1 to 14.0.3 in docker/login-action#1096

Full Changelog: docker/login-action@v4.6.0...v4.7.0

Commits

• 81c6f93 Merge pull request #1100 from docker/dependabot/npm_and_yarn/docker/actions-t...
• 1b16c8d Merge pull request #1096 from docker/dependabot/npm_and_yarn/uuid-14.0.3
• ac86b5e [dependabot skip] chore: update generated content
• 1476d84 build(deps): bump @​docker/actions-toolkit from 0.94.0 to 0.107.0
• 503cee6 Merge pull request #1095 from docker/dependabot/github_actions/actions/create...
• f093535 Merge pull request #1099 from docker/dependabot/github_actions/codecov/codeco...
• d5ae7f1 Merge pull request #1098 from docker/dependabot/github_actions/docker/bake-ac...
• 6f97507 Merge pull request #1097 from docker/dependabot/github_actions/docker/bake-ac...
• 006d61f Merge pull request #1094 from docker/dependabot/github_actions/codeql-actions...
• 93f5f52 Merge pull request #1093 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...
• Additional commits viewable in compare view

Updates pypa/cibuildwheel from 4.3.3 to 4.3.5

Release notes

Sourced from pypa/cibuildwheel's releases.

v4.3.5

• 🐛 Stops passing the target build environment to the host virtualenv call, regression in v4.3.4 (#3023)
• 🛠 Updates dependencies and constraints (pyodide-build 0.39.3, CPython 3.15.2, etc) (#3024, #3027)
• 💼 Updates CI actions (#3025)

v4.3.4

• 🔐 Warns when a uv build frontend is selected and the host uv is older than 0.13.4, which still trusts the compromised eMudhra CA roots (#3021)
• 🔐 Uses cibuildwheel's CA bundle for pip on Python 3.9, where pip uses its bundled certifi, which still trusts the compromised eMudhra roots (#3017)
• 🔐 Uses cibuildwheel's CA bundle for pip on GraalPy, where truststore is not supported (#3019)
• 🔐 Uses cibuildwheel's CA bundle in Android, iOS, and Pyodide cross venvs, where pip uses the host's OpenSSL CA file (#3020)
• 🐛 Seeds build's isolated environment with the pinned pip on macOS and Windows, fixing GraalPy 25.0 builds (#3018)
• 💼 Stops Azure cache growth from restoreKeys (#3022)

Changelog

Sourced from pypa/cibuildwheel's changelog.

v4.3.5

27 October 2026

• 🐛 Stops passing the target build environment to the host virtualenv call, regression in v4.3.4 (#3023)
• 🛠 Updates dependencies and constraints (pyodide-build 0.39.3, CPython 3.15.2, etc) (#3024, #3027)
• 💼 Updates CI actions (#3025)

v4.3.4

22 October 2026

• 🔐 Warns when a uv build frontend is selected and the host uv is older than 0.13.4, which still trusts the compromised eMudhra CA roots (#3021)
• 🔐 Uses cibuildwheel's CA bundle for pip on Python 3.9, where pip uses its bundled certifi, which still trusts the compromised eMudhra roots (#3017)
• 🔐 Uses cibuildwheel's CA bundle for pip on GraalPy, where truststore is not supported (#3019)
• 🔐 Uses cibuildwheel's CA bundle in Android, iOS, and Pyodide cross venvs, where pip uses the host's OpenSSL CA file (#3020)
• 🐛 Seeds build's isolated environment with the pinned pip on macOS and Windows, fixing GraalPy 25.0 builds (#3018)
• 💼 Stops Azure cache growth from restoreKeys (#3022)

Commits

• f9b966c Bump version: v4.3.5
• 7e3caea Update constraints (#3027)
• dff3913 chore(deps): bump the actions group with 2 updates (#3025)
• 2956993 fix: do not pass target environment to the host virtualenv call (#3023)
• 5d621c9 [Bot] Update dependencies (#3024)
• b9e566a Bump version: v4.3.4
• 0d511ac fix: use cibuildwheel's CA bundle in cross venvs (#3020)
• d6c9b11 feat: warn when uv is too old to have the eMudhra CA fix (#3021)
• 4463120 fix: seed build's isolated env with the pinned pip (#3018)
• 6d4911a fix: use cibuildwheel's CA bundle for pip on GraalPy (#3019)
• Additional commits viewable in compare view

Updates cachix/install-nix-action from 31.11.2 to 31.11.3

Release notes

Sourced from cachix/install-nix-action's releases.

31.11.3

This tag was incorrectly named. Prefer v31.11.3.

What's Changed

• nix: 2.35.3 -> 2.35.4 by @​xokdvium in cachix/install-nix-action#283 Security: Updates the bundled certificates shipped with the installer to remove the compromised eMudhra certificates.

Full Changelog: cachix/install-nix-action@v31.11.2...31.11.3

v31.11.3

What's Changed

• nix: 2.35.3 -> 2.35.4 by @​xokdvium in cachix/install-nix-action#283 Security: Updates the bundled certificates shipped with the installer to remove the compromised eMudhra certificates.

Re-release of 31.11.3, which was tagged incorrectly.

Full Changelog: cachix/install-nix-action@v31.11.2...v31.11.3

Commits

• 75c75c3 Merge pull request #283 from xokdvium/cacert-bump
• 3736037 nix: 2.35.3 -> 2.35.4
• See full diff in compare view

Updates SonarSource/sonarqube-scan-action from 8.3.0 to 8.4.0

Release notes

Sourced from SonarSource/sonarqube-scan-action's releases.

v8.4.0

What's Changed

• SQSCANGHA-174 NO-JIRA Bump actions/setup-node from 7.0.0 to 7.1.0 by @​dependabot[bot] in SonarSource/sonarqube-scan-action#277
• Update Rollup and preserve scanner argument compatibility by @​renovate[bot] in SonarSource/sonarqube-scan-action#275
• Update dependency rollup to v4.64.6 by @​renovate[bot] in SonarSource/sonarqube-scan-action#279
• SQSCANGHA-177 Update SonarScanner CLI to 8.2.0.6438 by @​github-actions[bot] in SonarSource/sonarqube-scan-action#281
• SQSCANGHA-176 docs: refresh action and scanner version examples by @​zglicz in SonarSource/sonarqube-scan-action#280
• Update dependency rollup to v4.64.7 by @​renovate[bot] in SonarSource/sonarqube-scan-action#282
• [CONTENT-3798] README update for marketing by @​tom-howlett-sonarsource in SonarSource/sonarqube-scan-action#274
• Update dependency rollup to v4.64.9 by @​renovate[bot] in SonarSource/sonarqube-scan-action#283
• Update dependency rollup to v4.64.12 by @​renovate[bot] in SonarSource/sonarqube-scan-action#288
• Update dependency rollup to v4.65.0 by @​renovate[bot] in SonarSource/sonarqube-scan-action#291
• SQSCANGHA-185 NO-JIRA Bump madhead/semver-utils from 5.0.0 to 5.1.1 by @​dependabot[bot] in SonarSource/sonarqube-scan-action#290
• Update SonarScanner CLI to 8.3.0.16463 by @​github-actions[bot] in SonarSource/sonarqube-scan-action#293

New Contributors

• @​zglicz made their first contribution in SonarSource/sonarqube-scan-action#280
• @​tom-howlett-sonarsource made their first contribution in SonarSource/sonarqube-scan-action#274

Full Changelog: SonarSource/sonarqube-scan-action@v8.3.0...v8.4.0

Commits

• 4d1dc0c Update SonarScanner CLI to 8.3.0.16463 (#293)
• ee2d757 SQSCANGHA-185 NO-JIRA Bump madhead/semver-utils from 5.0.0 to 5.1.1 (#290)
• a7de334 Update dependency rollup to v4.65.0 (#291)
• 38f0382 Update dependency rollup to v4.64.12 (#288)
• 54ae8f2 Update dependency rollup to v4.64.9 (#283)
• 3a63ba4 CONTENT-3798 README update for marketing (#274)
• b632445 Update dependency rollup to v4.64.7 (#282)
• c3c1d58 SQSCANGHA-176 docs: refresh action and scanner version examples (#280)
• b541427 SQSCANGHA-177 Update SonarScanner CLI to 8.2.0.6438 (#281)
• 15d1d91 Update dependency rollup to v4.64.6 (#279)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5c538c36-8686-4719-bf17-d409dceeb8be

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

[robertodr]

Automated approval for an automated PR

[github-actions]

Docs preview: https://pr-436.monoprop-docs.pages.dev

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.45%. Comparing base (8dac3a7) to head (97a3050).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #436   +/-   ##
=======================================
  Coverage   97.45%   97.45%           
=======================================
  Files          15       15           
  Lines         865      865           
  Branches      120      120           
=======================================
  Hits          843      843           
  Misses         16       16           
  Partials        6        6           

Flag	Coverage Δ
cpp	97.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[robertodr]

Automated approval for an automated PR

[github-actions]

Container image pushed to GHCR. Pull it with Docker or Singularity:

docker pull ghcr.io/algorithmiq/monoprop:pr-436-sapphirerapids
singularity pull monoprop_pr-436-sapphirerapids.sif docker://ghcr.io/algorithmiq/monoprop:pr-436-sapphirerapids

docker pull ghcr.io/algorithmiq/monoprop:sha-d6900e8-sapphirerapids
singularity pull monoprop_sha-d6900e8-sapphirerapids.sif docker://ghcr.io/algorithmiq/monoprop:sha-d6900e8-sapphirerapids

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud