chore(release): duroxide-node 0.1.26 — pick up duroxide-pg 0.1.33 native-tls fix#6
Merged
Merged
Conversation
Bumps duroxide-pg 0.1.32 → 0.1.33 to pick up the upstream native-tls fix (microsoft/duroxide-pg#8). Released duroxide-pg 0.1.32 was missing the native-tls reqwest feature, so HTTPS calls — including the AAD token acquisition that powers connectWithEntra and connectWithSchemaAndEntra — failed at runtime with 'error sending request' / 'invalid URL, scheme is not http'. No public API changes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
2 participants
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 duroxide-pg
0.1.32→0.1.33to pick up the upstream native-tls fix from microsoft/duroxide-pg#8.Why
Released
duroxide-pg 0.1.32pulledreqwesttransitively without a TLS connector compiled in. As a result every HTTPS call inside the crate — including the AAD token acquisition that powersPostgresProvider.connectWithEntra/connectWithSchemaAndEntra— failed at runtime with errors like:This was discovered while validating PilotSwarm's passwordless Entra migration end-to-end on AKS Workload Identity. The patched binary (built locally against
duroxide-pg 0.1.33) resolves the issue: workers connect to Azure Database for PostgreSQL via Entra cleanly with no errors.Changes
Cargo.toml:duroxide-pg0.1.32→0.1.330.1.25→0.1.26CHANGELOG.md: new[0.1.26]entrypackage-lock.json: regeneratedNo API changes
This is a pure dependency / release bump. No code changes in this repo. After merge + tagged release, the
publishworkflow rebuilds platform binaries against the fixedduroxide-pg.Validation
End-to-end validated by:
duroxide-nodelocally with[patch.crates-io] duroxide-pg = { path = ... }pointing at the fix branch.duroxide.linux-x64-gnu.nodeinnode:24-trixieDocker.1/1 Runningwith no Entra/TLS errors.Related