Repository navigation
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
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.
Regenerated the SDK and native core libraries from SDK core
677fbba2(beta channel). This is the core for the upcoming0.4.3b1beta.Warning
Known problem: the native libraries are in the wrong folders, so the Linux and Windows test jobs are expected to fail. The SDK loads its library from
src/onepassword/lib/<arch>/. This branch, generated by the SDK core publish job, has:libop_uniffi_core.so, the Windowsop_uniffi_core.dlland an extraop_uniffi_core.pyatsrc/onepassword/lib/root.soor.dllinx86_64/oraarch64/.soat allOnly the macOS
.dylibfiles are in the right place.The cause is in the core publish pipeline: its build artifacts lose their arch folder on upload, and are all downloaded into one folder. Every Python branch generated since May 2026 has this problem. Don't merge until the libraries are fixed, either by regenerating from a fixed pipeline or by adding the correct libraries to this branch.
What's in it
Fix: secret references that use a Personal vault's account-type name now resolve. For example,
op://Employee/...on a Team or Business account, as copied from the desktop app's "Copy Secret Reference". Before this fix they failed with "no vault matched the secret reference query".This is the first core update since
v0.4.1, which shipped core3d49ce29. It keepsv0.4.2's eMudhra CA distrust fix on Linux (rustls-webpki0.103.16,webpki-root-certs1.0.10). The generated API only adds things:AuthExpiredException(errors.py)VaultAccessorType.BROKER(types.py)No methods are added or removed.
The generator also reformatted examples, the README and some wrapper files (ruff). That's formatting only.
Notes
beta, notmain, like earlier betas. The0.4.3b1release PR is stacked on this one, andbetamerges intomainbefore the next stable release.🤖 Generated with Claude Code