Release xy@0.0.8

[github-actions]

Materialized changelogs for release action release-patch (dispatched on main).

Package	Current	Next	Tag
xy	0.0.7	0.0.8	v0.0.8

Merging this PR lands the versions above for release: the push to main
triggers the release_from_changelog.yml workflow, which builds each package and
then waits for pypi environment approval before uploading; the tag and
GitHub release are created only after a successful upload. If a publish
fails, fix the problem on top of the changelog bump — the next push retries
automatically.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 035e3386-dd16-4552-b0f2-db8cf67b0673

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codspeed]

Merging this PR will not alter performance

⚠️ 13 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• test_memory_report_composed_layered_core_2d
• test_first_payload_heatmap_core_2d
• test_first_payload_scatter_small
• test_first_payload_composed_layered_core_2d
• test_build_styled_panel_raw
• test_build_bar_categorical_pyplot
• test_first_payload_wind_rose
• test_build_line_small_raw
• test_first_payload_bar_core_2d
• test_build_bar_categorical_raw
• …and 3 more

ℹ️ 109 benchmarks have no flame graph

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

• test_selection_rows_message_crossfilter
• test_memory_report_composed_layered_core_2d
• test_delaunay_unstructured_topology
• test_transport_decode_frame_direct
• test_transport_decode_frame_density
• test_indexed_triangle_expansion
• test_m4_indices_zoom
• test_animation_encode_100k_stable_keys
• test_first_payload_heatmap_core_2d
• test_pick_hover_categorical_readout
• …and 99 more

✅ 109 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing release/release-patch-38441716411 (a426ca5) with main (5631f83)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩