Bump mssql-py-core to 0.1.8 - #155
Merged
Merged
Conversation
saurabh500
approved these changes
Jul 29, 2026
📊 Code Coverage Report
Diff CoverageDiff: main...HEAD, staged and unstaged changesNo lines with coverage information in this diff. 🔗 Quick Links |
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
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.
Bumps
mssql-py-corefrom 0.1.7 to 0.1.8.Why: The Arrow bulk copy feature (#95) merged into
mainwithout a version bump —0.1.7was already claimed by the CLR UDT fix (#111). Publishing the Arrow-enabled wheel needs a fresh version so the published native artifact stays immutable/traceable andmssql-pythoncan pin the Arrow build explicitly.Scope: version string only.
mssql-py-core/Cargo.lockis gitignored and the crate is workspace-excluded, so no lockfile changes. Follow-up: bump the py-core pin inmssql-pythonto 0.1.8 once the 0.1.8 wheel is published.