chore: bump bb version

[Savio-Sou]

Description

Summary*

Bump bb version tested.

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 3710be5	Previous: 9808525	Ratio
rollup-checkpoint-merge	0.004 s	0.003 s	1.33

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		registry-auth-token@3.3.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/registry-auth-token@3.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/registry-auth-token@3.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

Changes to circuit sizes

Generated at commit: 38fc33cd6e295483b618d68ce6cc6c0a20757e1a, compared to commit: 9808525b4f420397ea30ba91293ffb6539668e3f

🧾 Summary (10% most significant diffs)

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
regression_7744	0 ➖	0.00%	+11 ❌	+11.00%
bench_eddsa_poseidon	0 ➖	0.00%	+1,016 ❌	+4.71%
function_ref	0 ➖	0.00%	+3 ❌	+3.80%

---

Full diff report 👇

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
regression_7744	8 (0)	0.00%	111 (+11)	+11.00%
bench_eddsa_poseidon	17,696 (0)	0.00%	22,602 (+1,016)	+4.71%
function_ref	25 (0)	0.00%	82 (+3)	+3.80%
regression_5045	11 (0)	0.00%	1,282 (+22)	+1.75%
bench_ecdsa_secp256k1	163 (0)	0.00%	41,717 (+275)	+0.66%
ecdsa_secp256k1	163 (0)	0.00%	41,717 (+275)	+0.66%
ecdsa_secp256k1_invalid_pub_key_in_inactive_branch	227 (0)	0.00%	41,781 (+275)	+0.66%
embedded_curve_ops	13 (0)	0.00%	5,368 (+18)	+0.34%
bit_shifts_runtime	467 (0)	0.00%	4,760 (+10)	+0.21%
ecdsa_secp256r1_3x	487 (0)	0.00%	206,390 (+114)	+0.06%
ecdsa_secp256r1	163 (0)	0.00%	71,296 (+37)	+0.05%
ecdsa_secp256r1_invalid_pub_key_in_inactive_branch	227 (0)	0.00%	71,360 (+37)	+0.05%
slice_dynamic_index	799 (0)	0.00%	5,097 (+2)	+0.04%
inactive_signed_bitshift	79 (0)	0.00%	2,879 (+1)	+0.03%
bit_shifts_comptime	51 (0)	0.00%	2,943 (+1)	+0.03%
regression_struct_array_conditional	68 (0)	0.00%	3,214 (+1)	+0.03%

[TomAFrench]

Handled in #10359