Release version 0.1.2 - #75
Merged
Merged
Conversation
Patch release carrying the Windows publication fix from #73: the directory durability barrier is skipped on win32, where no POSIX directory fsync equivalent exists, so uploads no longer fail with EPERM. All enforced version touchpoints move to 0.1.2 and the site release references follow.
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.
Patch release for the Windows publication fix (#73 / issue #42):
syncDirectory()now skips the directory durability barrier on win32, so uploads no longer fail with EPERM and publishing works on Windows.Bumps every touchpoint the release-version gate enforces to 0.1.2 (root + adapter packages, Helm chart version/appVersion/image tag, MCP server version, channel protocol version) plus the site's release references, and corrects the docs aside to say "current release" now that v0.1.1 was the first.
Verified locally:
check:release-version --tag v0.1.2andverify:sitepass. After merge: annotated tagv0.1.2triggers the release workflow (npm step skips; adapters republished locally by the maintainer).