You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three problems come from the first two pre-releases.
CHANGELOG.md holds no section for 2.0.0-rc.2. Add one, or fold the content into the 2.0.0 section.
The release notes of rc2 hold only a compare link. Write real notes for each later pre-release.
The tag name and the crate version disagree. The tags read v2.0.0-rc1 and v2.0.0-rc2. Cargo.toml reads 2.0.0-rc.2. The workflow comments read v2.0.0-rc.1. Pick one form and use it.
Check the container image for linux/amd64 and linux/arm64.
Check @beacon/client on the npm latest tag.
Check beacon-datalake-cli on PyPI.
Write the GitHub release notes.
Upgrade the public demo node at beacon-wod.maris.nl.
Update the example repository.
A v* tag starts three workflows: publish-beacon-server, publish-beacon-datalake-cli and publish-beacon-ts. The tag is the only trigger, so a version file with a wrong value fails the run.
Beacon 2.0.0 is the next major release. Version 1.8.0 came out on 2026-06-29.
This issue tracks every task before the 2.0.0 release.
Two pre-releases are done. The third pre-release is planned for this week.
Pre-releases
Three problems come from the first two pre-releases.
CHANGELOG.mdholds no section for2.0.0-rc.2. Add one, or fold the content into the 2.0.0 section.v2.0.0-rc1andv2.0.0-rc2.Cargo.tomlreads2.0.0-rc.2. The workflow comments readv2.0.0-rc.1. Pick one form and use it.Features in 2.0.0
Engine
Formats
Clients and interfaces
beacon-mcp, an MCP server for LLM clients (Add MCP server (beacon-mcp): expose tables to Claude over streamable HTTP #323, MCP: export_query tool + guard rails for large results #325)CREATE SECRETfor object store credentialsATTACHfor a remote Beacon catalogOpen work, wanted in 2.0.0
SET, not only with a restart (Change a setting with SET, not only with a restart #372, Allow runtime settings to be changed with SET, not only env vars #359)UNRELEASED_PAGESindocs/.vitepress/config.mtsstill hides it, but the feature ships.Open work, decide before the release
SELECT(Add util functions for masking in select #97)Bugs to fix
Blockers
Both bugs return a wrong result, not a slow result. A major release must not ship them.
Wanted, not a blocker
coalescereturns an empty result (JSON query: a multi-argument coalesce returns an empty result on the exv collection #366)Incompatible changes
State each change in the release notes, and in an upgrade page.
beacon-datalake/is nowbeacon-server/.beacon-datalake-clients/is nowbeacon-clients/.BEACON_S3_DATA_LAKEis nowBEACON_S3_DATASETS. The old name still works.ST_Transform.beacondbwheel is no longer published.Tests
Complete tests gate the release. #399 plans the work.
integration-tests/README.mdRelease steps
2.0.0section inCHANGELOG.md.2.0.0inCargo.toml.2.0.0inbeacon-clients/beacon-ts/package.json.2.0.0inbeacon-clients/beacon-datalake-cli/pyproject.toml.2.0.0inbeacon-db/beacon-db-py/pyproject.toml. The wheel stays unpublished.docs/docs/2.0.0-rc2/todocs/docs/2.0.0/.2.0.0-rc2link indocs/.vitepress/config.mts.LATEST_VERSIONto2.0.0indocs/.vitepress/theme/version.js.cargo +1.94 fmt --checkandcargo +1.94 clippy --workspace.cargo +1.94 test --workspace.integration-tests/run.sh.cargo audit. Record every advisory that stays open.v2.0.0, and push the tag.@beacon/clienton the npmlatesttag.beacon-datalake-clion PyPI.A
v*tag starts three workflows:publish-beacon-server,publish-beacon-datalake-cliandpublish-beacon-ts. The tag is the only trigger, so a version file with a wrong value fails the run.Out of scope
These issues move to 2.1.0.
beacon.db(Consolidate the in-memory file statistics cache onto the beacon.db statistics store #368)libcudf-rs#231)