Skip to content

[Backport perf-v17] chore(deps): update scylladb/cassandra-stress docker tag to v3.20.7#14984

Open
scylladbbot wants to merge 1 commit into
scylladb:branch-perf-v17from
scylladbbot:backport/14771/to-perf-v17
Open

[Backport perf-v17] chore(deps): update scylladb/cassandra-stress docker tag to v3.20.7#14984
scylladbbot wants to merge 1 commit into
scylladb:branch-perf-v17from
scylladbbot:backport/14771/to-perf-v17

Conversation

@scylladbbot

Copy link
Copy Markdown

This PR contains the following updates:

Package Update Change
scylladb/cassandra-stress patch 3.20.63.20.7

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

scylladb/cassandra-stress (scylladb/cassandra-stress)

v3.20.7

Compare Source

What's Changed

  • chore(deps): update dependency com.scylladb:java-driver-core-shaded to v4.19.0.9 by @​renovate[bot] in #​156
  • chore(deps): update dependency com.scylladb:scylla-driver-core to v3.11.5.15 by @​renovate[bot] in #​154

Full Changelog: scylladb/cassandra-stress@v3.20.6...v3.20.7


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

  • (cherry picked from commit 168ab44)

Parent PR: #14771

@fruch

fruch commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@juliayakovlev let's do a subset of the perf test with this, to see it's doesn't regress the pref tests

@juliayakovlev

Copy link
Copy Markdown
Contributor

@juliayakovlev let's do a subset of the perf test with this, to see it's doesn't regress the pref tests

@fruch do you want to run official job with new c-s image or in staging?

@fruch

fruch commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@juliayakovlev let's do a subset of the perf test with this, to see it's doesn't regress the pref tests

@fruch do you want to run official job with new c-s image or in staging?

I think staging would be better, we don't want to mix our official results with it, not yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants