Skip to content

release: v0.3.0 - #155

Merged
vyncint merged 6 commits into
mainfrom
release/v0.3.0
Nov 18, 2026
Merged

vyncint merged 6 commits into
mainfrom
release/v0.3.0

Conversation

@vyncint

@vyncint vyncint commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Release 0.3.0, per docs/RELEASING.md. Main has taken every fix (#135, #137–#141, #143–#147, #149–#154); this PR changes no code.

Release mechanics

  • The workspace moves to 0.3.0: [workspace.package], every internal version, and the lockfile's nine entries.
  • The CHANGELOG's [Unreleased] becomes [0.3.0] - 2026-11-18, with an introduction and repointed link definitions. .github/scripts/extract-changelog.sh 0.3.0 prints the section: 810 lines, 51.5 KB.

CHANGELOG repair. Every fix PR added a ### Fixed heading of its own, so main had seven. Seven bullets also sat under Fixed although their fix branches filed them under Changed: two marked Breaking (TelemetrySnapshot.operator_totals, #102), plus API and default changes (BufferLayout::padded_len, #90, #46, the CUDA aggregate's read-back, #134, #148). Each kind now has one heading, and those bullets are under Changed, as the CHANGELOG's preamble promises for every breaking change. A script checked that no line of text was added, lost or duplicated.

Docs truth pass

Before tagging

One test fix. On this PR's first CI run, the macOS job failed the_static_planner_runs_lowered_nodes_correctly. Its telemetry witness counted two GpuHashJoinExec of 2019 rows each where its COUNT(*) join ran one, because distributed_results_equal_embedded_results was running the same join in a parallel thread of the same process. The rows were right, so this was a race in the test, not in the product. Every test in tests/cluster.rs that runs cluster queries now holds one tokio mutex for its whole run. A flake there would also stall release.yml's CI gate before publishing.

CUDA, per RELEASING step 0. No gpu runner is registered (#38), so gpu.yml cannot run, and the release notes say exactly what did run instead: a Tesla T4 (driver 595.71.05, CUDA 13.2) on 2026-11-18, three passes, on the fix branches before they merged. All of them passed:

  • device suite with ignored tests: 43 passed;
  • compute with --include-ignored under OXIDE_BACKEND=cuda, including conformance, join_timing and aggregate_timing;
  • the runtime suite;
  • special_floats and vector_null_elements on the device.

#28, #29, #45 and #46 ran on a Tesla T4 on 2026-11-18 before they
merged; the chain bump (#40) retired the thrift advisory (#4, #54);
#31 landed with #148's fail-fast. Three lines remain: double-buffered
transfers, TLS for the cluster ports (#30, whose private-network half
shipped) and a runner for gpu.yml (#38).

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
gpu.yml, docs/RELEASING.md step 0, the test-cuda-device comment and the
README's CUDA line named the 2026-09-06 session as the only device run.
0.3.0's CUDA changes ran on a T4 on 2026-11-18, on the fix branches
before they merged. RELEASING now asks a release with no gpu runner to
say exactly what ran (ADR-0012) rather than only 'compiled-only'.

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
[workspace.package] and every internal version in
[workspace.dependencies]; the lockfile's nine oxidelake entries follow.

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
STATUS: the header describes 0.3.0; the matrix records the 2026-11-18
T4 session (on the fix branches before they merged, not the tagged
commit) in the CUDA kernel, hash join, aggregation and operator rows,
which moved out of the compiled-only and needs-GPU columns; a Known
limitations section names #142 (NaN pruning, apache/datafusion#15812)
and #148 (Ballista 55's lost-worker rollback) with their workarounds;
two decision bullets that later ones superseded (cudarc without the
NVRTC probe, spill accounting before #116) are gone.

README: the status line describes 0.3.0.
Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
CHANGELOG: [Unreleased] becomes [0.3.0] - 2026-11-18, with an
introduction (what the release is, how its CUDA paths were verified,
the two known upstream issues) and the link definitions repointed.

Its sections are consolidated to one heading each. The fix PRs each
added a '### Fixed' heading of their own, so main had seven, and seven
bullets had landed under Fixed that their fix branches filed under
Changed: two marked Breaking (TelemetrySnapshot.operator_totals, #102)
and API or default changes (BufferLayout::padded_len, #90, #46, the
CUDA aggregate's read-back, #134, #148). They are under Changed now,
as the preamble promises for every breaking change. No line of text
was added, lost or duplicated by the move (checked).

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
@vyncint vyncint added this to the v0.3.0 milestone Nov 18, 2026
…e hub

The witnesses in tests/cluster.rs count the Gpu*Exec operators the
process-wide telemetry hub registered from an id on, and the file's
tests run in parallel threads of one process. On the release PR's macOS
runner, the_static_planner_runs_lowered_nodes_correctly counted two
GpuHashJoinExec of 2019 rows each where its COUNT(*) join ran one:
distributed_results_equal_embedded_results was running the same t ⋈ r
join at the same moment. The rows were right; the witness was not.

Every test that runs queries on a cluster now holds one tokio mutex for
its whole run (tokio's, because the guard lives across awaits). Three
local runs of --test cluster: 7 passed each, about 8 s, up from 2 s.

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
@vyncint
vyncint merged commit b534d65 into main Nov 18, 2026
19 checks passed
@vyncint
vyncint deleted the release/v0.3.0 branch November 18, 2026 11:08
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.

1 participant