Repository navigation
docs: post-0.5.2 release fixes (notes disclaimer, README writer, sidebar labels) - #116
Merged
Merged
Conversation
v0.5.2 is now cut and published, so the release-notes section no longer carries the pre-release "under active development -- may change before release" disclaimer. The `Current version: 0.5.2` banner is unchanged. Co-authored-by: Isaac <no-reply@databricks.com>
The LiDAR LAS/LAZ writer (new in 0.5.2) was present in the Readers table but missing from Writers; add the lightweight-only row so the README reflects the registered writer. Co-authored-by: Isaac <no-reply@databricks.com>
The exif/file/lidar reader & writer pages appended the redundant `*_gbx` DataSource id to their sidebar_label, diverging from the bare-format-name convention the other 10+ pages use -- and leaving the LiDAR reader labeled `LiDAR (lidar_gbx)` while its writer was just `LiDAR`. Drop the `(exif_gbx)` / `(file_gbx)` / `(lidar_gbx)` suffixes. `GeoJSONL (multi-file)` is kept: it is an informative descriptor, not a redundant DataSource id. Co-authored-by: Isaac <no-reply@databricks.com>
mjohns-databricks
temporarily deployed
to
runtime
October 7, 2026 20:12 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
mjohns-databricks
temporarily deployed
to
runtime
October 7, 2026 20:12 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mjohns-databricks
temporarily deployed
to
runtime
October 7, 2026 20:43 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mjohns-databricks
temporarily deployed
to
runtime
October 7, 2026 20:43 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Post-release documentation fixes for v0.5.2 (docs/README only — no code, no re-tag). Merging re-deploys the docs site and refreshes the README.
Under development … may change before releasebanner from the now-publishedv0.5.2section (docs/docs/release-notes.mdx); theCurrent version: 0.5.2banner is unchanged.lidar_gbxLAS/LAZ writer (new in 0.5.2) to the Readers & Writers → Writers table — it was in the Readers table but missing from Writers.(*_gbx)suffixes the exif/file/lidar pages had added (which also left the LiDAR reader labeled but the writer not).GeoJSONL (multi-file)is kept as an informative descriptor.This pull request and its description were written by Isaac.