Skip to content

docs: retarget binding to the LadybugDB org repo (+ LICENSE)#2

Merged
adsharma merged 2 commits into
LadybugDB:mainfrom
sergey-v9:docs/retarget-to-org
May 30, 2026
Merged

docs: retarget binding to the LadybugDB org repo (+ LICENSE)#2
adsharma merged 2 commits into
LadybugDB:mainfrom
sergey-v9:docs/retarget-to-org

Conversation

@sergey-v9
Copy link
Copy Markdown
Collaborator

Summary

  • The C# binding was adopted into the LadybugDB org as LadybugDB/ladybug-dotnet. This PR removes every remaining personal-repo (sergey-v9/...) reference and retargets the docs/config to the org repo:
    • living notes: .agents/notes/DECISIONS.md, HANDOFF.md, ROADMAP.md
    • release.yml trusted-publishing header comment (owner=LadybugDB)
    • nuget/nuget-package.props RepositoryUrl
  • Documents the new ci.yml native-test matrix (added in 0a8d3d2) and pins the docs to ENGINE_VERSION = v0.17.0, matching release.yml.
  • Drops the now-stale "temporary/personal home, dry-run until adoption" framing; adds D17 recording the org adoption + native CI matrix.
  • LICENSE: keeps the original author and adds Ladybug Contributors.

Notes

  • Docs/metadata only — no managed code, interop, struct layout, or test changes. The pinned ABI and ENGINE_VERSION are unchanged.

Test plan

  • build-test (both TFMs + ABI/struct-layout guards + pack smoke) stays green.
  • native-test matrix (linux-x64 + win-x64) still loads the native engine and runs the suite with LADYBUG_REQUIRE_NATIVE=1.

sergey-v9 added 2 commits May 30, 2026 19:55
The binding was adopted into the LadybugDB org as LadybugDB/ladybug-dotnet. Replace all personal-repo (sergey-v9) references in the living notes, the release workflow header, and the nuget RepositoryUrl with the org repo, and document the new ci.yml native-test matrix plus the v0.17.0 ENGINE_VERSION pin.
@sergey-v9
Copy link
Copy Markdown
Collaborator Author

@adsharma would you mind giving me collaborator access (Write / Maintain) to that repo so I can commit it right away, or do you prefer to keep me posting changes as PRs?

Next, I plan to set up NuGet native package builds separately for different platforms and configure publishing them to NuGet feed.

@adsharma
Copy link
Copy Markdown
Contributor

@sergey-v9 I've added you to this repo with write access. But let's use the PR process like all other repos.

Yes, Nuget packages will be great.

@adsharma adsharma merged commit 8a9d762 into LadybugDB:main May 30, 2026
3 checks passed
@sergey-v9
Copy link
Copy Markdown
Collaborator Author

@adsharma Great, thanks. Got it, I'll do all further work through PRs.

@sergey-v9 sergey-v9 deleted the docs/retarget-to-org branch May 30, 2026 18:41
@adsharma
Copy link
Copy Markdown
Contributor

@sergey-v9 I've also setup LadybugDB org on nuget and added permissions to release.yml to publish packages via the trusted publishing path.

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.

2 participants