Prepare 0.17.0.1 release#5
Merged
Merged
Conversation
Add runnable C# examples for quickstart queries, CSV graph loading, prepared statements, and result materialization so consumers can exercise the published package API.
Move the package family to the stable 0.17.0.1 revision scheme, derive engine releases from the first three package segments, and replace the development note files with a maintained repository guide.
Contributor
|
LGTM except for a question about the versioning scheme. Nuget packages seem to follow semver, which suggests 0.17.0-1 instead of 0.17.0.1. Is this something you considered? |
Collaborator
Author
I considered |
sergey-v9
added a commit
to sergey-v9/ladybug-dotnet
that referenced
this pull request
Jun 29, 2026
…hiti wishes LadybugDB#3, LadybugDB#5) Wish LadybugDB#5: add a structured `consumer_impact=` one-liner to upstream-engine.pin for the current pin (interop/fts_scoring/new_ddl/fixes/note), and make it a REQUIRED field on every bump in docs/upstream-sync.md — a new numbered pin-advance step plus the field format and per-field guidance, so consumers read the impact off the pin instead of re-deriving it each cycle. Wish LadybugDB#3: add a "D) Engine-feature backlog (needs upstream)" section to docs/upstream-sync.md recording the fixed-size FLOAT[N] parameter-binding ask: the binding cannot do it alone because lbug.h has no fixed-ARRAY value constructor (only lbug_value_create_list) and the header is byte-identical v0.17.1..main, so 0.18.0 adds none either; it needs an upstream lbug_value_create_array-style addition plus a typed binding helper. Until then the List<float> + CAST($v AS FLOAT[N]) path (pinned by Vector_InlineCosineSimilarity) is the supported route. Also append a "Response — 2026-06-29 (binding maintainers)" section to GRAPHITI_SEARCH_EXTENSIONS_FEEDBACK.md addressing all six wishes by number: LadybugDB#1 Linux from-source native build fixed (validated by next dev push), LadybugDB#2 version-tolerant DROP_FTS_INDEX round-trip, LadybugDB#3 engine-gated/backlogged, LadybugDB#4 Connection.ExecuteMany shipped, LadybugDB#5 consumer_impact added+required, #6 FTS ranking assertions hardened to a score-tweak-resilient cross-check. Docs-only; build clean (0 warnings, both TFMs), suite green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Stabilize package versioning and maintainer docs
Summary
0.17.0-alpha.1to stable0.17.0.1.0.17.0.1->v0.17.0)..agents/notes/files withMAINTAINING.md.README.md,AGENTS.md, and example package-version defaults to match the stable fourth-segment versioning policy.Test plan
dotnet build LadybugDB.slnx -c Releasedotnet run --project cake/LadybugDB.Build.csproj -- --target Pack --engine-version v0.17.0Notes
examples/database-usage-samples; otherwise retarget it tomain.0.17.0.1version.