Clean up direct-binary release and update paths#306
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.
Summary
VERSIONfile and keep release notes branded as Every Codecodex-cli/npm wrapper/staging path and mark it permanently removed for upstream importsReview Notes
Agent review found no blockers after follow-up fixes. One branch-introduced Windows-style path edge case was addressed by normalizing direct-binary path and command-name handling, with tests.
A TypeScript SDK compile issue was flagged by one agent, but it exists on
mainunchanged and this branch does not touchsdk/typescript; it is out of scope for this release cleanup.Validation
./build-fast.sh./pre-release.sh