Release v0.1.1: consolidate post-0.1.0 work into one version#20
Merged
Conversation
We never tagged the intermediate 0.1.1 / 0.1.2 versions in git or pushed them to the registry, so Registrator AutoMerge would flag a 0.1.0 → 0.1.2 jump. This consolidates every unreleased change since v0.1.0 (the rename, unified-Live multi-schema streaming, exponential backoff, live capture durability, do-block APIs, Documenter site, CHANGELOG) under a single 0.1.1 release. Bumps Project.toml version 0.1.2 → 0.1.1, rewrites CHANGELOG so the 0.1.1 entry contains every Added/Changed/Fixed bullet from the prior 0.1.1 + 0.1.2 + Unreleased sections, and updates the README status line. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue. |
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.
We never tagged 0.1.1 or 0.1.2 in git or pushed them to the registry. Going 0.1.0 → 0.1.2 would make Registrator AutoMerge flag a version skip, so this PR consolidates every unreleased change since v0.1.0 under a single 0.1.1 release.
Changes
After merge
🤖 Generated with Claude Code