Prepare Dander 0.3.0rc1 - #55
Merged
Merged
Conversation
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.
What changed
0.3.0rc1.Runtime boundary
This is a release-preparation-only change.
src/danderis byte-for-byte unchanged from mergedmain. It does not tag, publish, deploy, apply Terraform, or modify any schedule.NetSuite remains explicitly simulator-validated and is not represented as real-tenant support.
Validation
uv lock --checkuv run ruff check .uv run ruff format --check .uv run mypy src testsuv run pytest— 677 passed0.3.0rc1, generated source-free projects pinned to the candidate, and validatedPrior capability acceptance
Merged Odoo and Salesforce each completed source-free live acceptance against disposable systems. Replay remained duplicate-free, cursors were monotonic, transforms/tests and metadata completed, and leases cleared. Sanitized evidence is recorded in issue #26 without any retained schedule change.
Do not merge, tag, publish, or deploy without separate direction.