Repository navigation
Release 0.1.0rc2 - #36
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.
Release candidate
Prepare the second public release candidate of
ebus-evidence.Version
This PR only changes the two canonical version locations:
pyproject.toml;src/ebus_evidence/__init__.py.The existing version-consistency test must keep both aligned.
Public changes since rc1
Raw-log transport hardening
The transport hardening was independently exercised against the same 4,818,571-line static real-world dataset. The final #28 run recovered exactly the affected 3,212 ebusd-initiated logger-artifact transactions while leaving established Evidence unchanged.
Bundle and local-input robustness
Beginner/install reliability
.venvpaths are never deleted automatically;Release and contributor validation
Current CI now exercises:
The required
beginner-flowmerge gate also requires both release-smoke prerequisites to have completed successfully.Scope
No new Evidence semantics, profile checks or heating-system behaviour are introduced by this release-preparation PR.
The existing
v0.1.0rc1tag must remain unchanged.