Repository navigation
chore: back-merge main (v0.8.1) into develop - #363
Merged
Merged
Conversation
chore(release): v0.8.1
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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
1 participant
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
Back-merge of
main(v0.8.1 release merge commit) intodevelop, plus docs recording the release.Why
Keeps
developcontaining the release merge commit; README status already says v0.8.1 (done in the bump PR).Changes
origin/mainintodevelopdocs/epics.md: 0.8.1 entryAGENTS.md§8: crates.io fact now 0.8.1 (verified 2026-10-09 via the crates.io API; publish run succeeded)Testing
Docs-only on top of the merge;
tole-coreandtole-cli0.8.1 verified on crates.io.🤖 Generated with Claude Code