Skip to content

chore(deps, amber): update pekkoversion to v1.7.0 - #7895

Open
renovate-bot wants to merge 2 commits into
apache:mainfrom
renovate-bot:renovate/pekkoversion
Open

chore(deps, amber): update pekkoversion to v1.7.0#7895
renovate-bot wants to merge 2 commits into
apache:mainfrom
renovate-bot:renovate/pekkoversion

Conversation

@renovate-bot

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
org.apache.pekko:pekko-actor (source) minor 1.6.01.7.0
org.apache.pekko:pekko-cluster (source) minor 1.6.01.7.0
org.apache.pekko:pekko-cluster-metrics (source) minor 1.6.01.7.0
org.apache.pekko:pekko-cluster-tools (source) minor 1.6.01.7.0
org.apache.pekko:pekko-multi-node-testkit (source) Test minor 1.6.01.7.0
org.apache.pekko:pekko-persistence (source) minor 1.6.01.7.0
org.apache.pekko:pekko-remote (source) minor 1.6.01.7.0
org.apache.pekko:pekko-slf4j (source) minor 1.6.01.7.0
org.apache.pekko:pekko-testkit (source) Test minor 1.6.01.7.0

Release Notes

apache/pekko (org.apache.pekko:pekko-actor)

v1.7.0

Compare Source


Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • "before 8am on monday"
  • 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 these updates again.


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

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

@forking-renovate forking-renovate Bot added the dependencies Pull requests that update a dependency file label Aug 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • Contributors with relevant context: @kz930
    You can notify them by mentioning @kz930 in a comment.

@codecov-commenter

Copy link
Copy Markdown

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@github-actions

github-actions Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

⚠️ Benchmark changes need a look

🟢 0 better · 🔴 4 worse · ⚪ 11 noise (<±5%) · 0 without baseline

Compared against main 2113455 benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.

Dashboard · Run

config throughput MB/s latency max Δ latest / 7d
🔴 bs=10 sw=10 sl=64 375 0.229 26,070/33,511/33,511 us 🔴 +9.1% / 🔴 +133.8%
🔴 bs=100 sw=10 sl=64 788 0.481 126,741/151,283/151,283 us 🔴 +5.6% / 🔴 +52.1%
bs=1000 sw=10 sl=64 914 0.558 1,091,173/1,199,313/1,199,313 us ⚪ within ±5% / 🔴 +25.1%
Baseline details

Latest main 2113455 from same runner

config metric PR latest main 7d avg Δ latest Δ 7d
bs=10 sw=10 sl=64 throughput 375 tuples/sec 405 tuples/sec 833.1 tuples/sec -7.4% -55.0%
bs=10 sw=10 sl=64 MB/s 0.229 MB/s 0.247 MB/s 0.508 MB/s -7.3% -55.0%
bs=10 sw=10 sl=64 p50 26,070 us 23,887 us 11,860 us +9.1% +119.8%
bs=10 sw=10 sl=64 p95 33,511 us 32,063 us 14,334 us +4.5% +133.8%
bs=10 sw=10 sl=64 p99 33,511 us 32,063 us 18,194 us +4.5% +84.2%
bs=100 sw=10 sl=64 throughput 788 tuples/sec 824 tuples/sec 1,085 tuples/sec -4.4% -27.4%
bs=100 sw=10 sl=64 MB/s 0.481 MB/s 0.503 MB/s 0.662 MB/s -4.4% -27.4%
bs=100 sw=10 sl=64 p50 126,741 us 119,996 us 92,973 us +5.6% +36.3%
bs=100 sw=10 sl=64 p95 151,283 us 147,310 us 99,460 us +2.7% +52.1%
bs=100 sw=10 sl=64 p99 151,283 us 147,310 us 107,737 us +2.7% +40.4%
bs=1000 sw=10 sl=64 throughput 914 tuples/sec 915 tuples/sec 1,111 tuples/sec -0.1% -17.8%
bs=1000 sw=10 sl=64 MB/s 0.558 MB/s 0.558 MB/s 0.678 MB/s 0.0% -17.7%
bs=1000 sw=10 sl=64 p50 1,091,173 us 1,084,704 us 915,816 us +0.6% +19.1%
bs=1000 sw=10 sl=64 p95 1,199,313 us 1,229,802 us 959,066 us -2.5% +25.1%
bs=1000 sw=10 sl=64 p99 1,199,313 us 1,229,802 us 993,644 us -2.5% +20.7%
Raw CSV
config_idx,batch_size,schema_width,string_len,num_batches,total_ms,total_tuples,total_bytes,tuples_per_sec,mb_per_sec,lat_p50_us,lat_p95_us,lat_p99_us
0,10,10,64,20,532.66,200,128000,375,0.229,26070.42,33511.04,33511.04
1,100,10,64,20,2539.24,2000,1280000,788,0.481,126740.94,151282.56,151282.56
2,1000,10,64,20,21879.83,20000,12800000,914,0.558,1091172.63,1199313.09,1199313.09

pekko-actor 1.7.0 raises its com.typesafe:config dependency from 1.4.6
to 1.4.9, and SBT's max-version-wins eviction carries that into the
amber dist over the 1.4.6 declared in common/{auth,config,workflow-core}.
config is a direct dep, so check_binary_deps.py failed the amber build
on version drift before the test step ever ran.

Bump the config bullet to 1.4.9 and refresh the eleven bundled pekko
jar bullets to 1.7.0 — the latter are informational in PR mode but the
strict nightly check would flag them. The common-module config
declarations stay at 1.4.6: raising them would evict 1.4.9 into the
other service dists that claim 1.4.6. No jars are added or removed and
both versions stay Apache-2.0, so NOTICE-binary is unaffected.
@forking-renovate

Copy link
Copy Markdown

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

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

Labels

dependencies Pull requests that update a dependency file engine

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants