Repository navigation
fix: bump locust from 2.46.0 to 2.47.0 - #2464
dependabot[bot] wants to merge 5 commits into
Conversation
Bumps [locust](https://github.com/locustio/locust) from 2.46.0 to 2.47.0. - [Release notes](https://github.com/locustio/locust/releases) - [Changelog](https://github.com/locustio/locust/blob/master/CHANGELOG.md) - [Commits](locustio/locust@2.46.0...2.47.0) --- updated-dependencies: - dependency-name: locust dependency-version: 2.47.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsRe-running this action after a short time may resolve the issue. See the documentation for more information and troubleshooting advice. OpenSSF Scorecard
Scanned Files
|
groupthinking
left a comment
There was a problem hiding this comment.
Review at head 73cff0fe: the Locust version in pyproject.toml changes but uv.lock does not. Both Python CI jobs fail at uv lock --check. Update and commit the lockfile, then rerun the exact-head checks.
Closes #2476 ## Summary - Compare the exact pull request base and head dependency inputs. For supported lockfile changes, submit focused snapshots for both revisions with the same scope and correlator. - For the root npm lockfile, include declared workspace manifests in both snapshots. If any changed npm manifest is not covered by a changed lockfile, use the full scan. - Keep the full-tree scan for mixed or unsupported dependency changes and pushes to `main`. Bound each Python requirements report to 120 seconds on that path so one file cannot consume the entire ten-minute job. If a report times out, Component Detection falls back to declared dependencies for that file, so its transitive graph can be incomplete. - Preserve the current severity and license policy and the evidence capture merged into `main` by #2409. ## Paths changed - `.github/workflows/dependency-review.yml` - `tests/unit/test_dependency_review_workflow.py` ## Validation - `uv run --no-project --with pytest --with pyyaml python -m pytest -q -o addopts='' tests/unit/test_dependency_review_workflow.py` — 14 passed after integrating latest `main`. - Ruff lint and format checks, plus `git diff --check` — passed. - [Hosted dependency review on head `24c8711`](https://github.com/groupthinking/EventRelay/actions/runs/40652875982) — passed, with no snapshot warning or dependency changes for this workflow/test-only diff. - Current head `2485239` contains the full-scan time bound. [All hosted pull request checks on this exact head](https://github.com/groupthinking/EventRelay/pull/2477/checks) have passed. The `main` push full-scan path has not been verified with this change. Once this repair reaches `main`, rerun dependency review on #2464 and #2465 before treating either as merge ready.
groupthinking
left a comment
There was a problem hiding this comment.
The earlier lockfile finding is addressed: pyproject.toml and uv.lock now agree on Locust 2.47.0, and both Python test jobs pass. I approve this code change at this head. The separate dependency-review evidence workflow still fails while recording/uploading its artifact, so this approval is not a merge recommendation until that required check is repaired.
Fixes #2475
Bumps locust from 2.46.0 to 2.47.0.
Release notes
Sourced from locust's releases.
... (truncated)
Changelog
Sourced from locust's changelog.
... (truncated)
Commits
66279c9Merge pull request #3569 from piyusha2005-bit/master508b2dcfix: don't crash the stats history CSV writer on workers with --csv-full-hist...94a369aMerge pull request #1 from piyusha2005-bit/fix-pytest-network-callsd6384datest: use local_http_server instead of www.locust.io in test_pytest_locustfilee2ad9a7fix: don't crash the stats history CSV writer on workers with --csv-full-history3a1d0caMerge pull request #3567 from charan-rathore/fix/csrf-stop-reset-post53a5a23Merge pull request #3565 from SulimanAbdulrazzaq/fix/mongodb-contrib-wrong-da...807f12dMerge pull request #3564 from SulimanAbdulrazzaq/fix/user-on-start-exception-...2417dfcMerge pull request #3563 from SulimanAbdulrazzaq/fix/eventhook-fire-iterates-...1dfbea4Merge pull request #3562 from SulimanAbdulrazzaq/fix/stoptest-library-mode-at...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)