release: prepare v0.2.9 mount fixes - #71
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
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.
Prepare v0.2.9 to ship the merged background mount readiness fix (#69) alongside the newly published Drive9 companion
a9acf30(mem9-ai/drive9#1013). The companion fixes an initial-sync lookup/attribute race that could still surface EAGAIN with the build checked for v0.2.8.This PR adds only release notes, including upgrade commands and the scope of both fixes. Installers and
ti updatekeep downloading the current published Drive9 CLI; no version pinning or distribution changes are included.Validation:
make testandmake e2epassed.make release-snapshotpassed with GoReleaser v2.18.2.a9acf30f555e22d0065b5cac92956505f8d34f7a, and supports the required layer and mount capabilities.git diff --checkpassed.Full cloud live-e2e was not rerun because this host has no configured API credentials. Upstream PRs document their respective real mount verification; the local version/capability checks do not establish combined cloud mount correctness.
After merge, publish an annotated
v0.2.9tag at the merged commit. Preserve v0.2.8 and its artifacts.