chore: publish to internal crate registry#2
Merged
Conversation
BatmanAoD
force-pushed
the
publish-tracing-error-to-rigetti-cargo
branch
from
5abb495 to
dc25a00
Compare
![windsurf-bot[bot]](https://avatars.githubusercontent.com/in/1066231?s=60&v=4){kind=small}
## Motivation CI `warnings` job (clippy) is failing with `error: manual implementation of "Option::zip"` for Rust 1.96.0. e.g. https://github.com/tokio-rs/tracing/actions/runs/25983660191/job/78456844423?pr=3534 ``` error: manual implementation of `Option::zip` --> tracing-error/src/backtrace.rs:208:41 | 208 | if let Some((file, line)) = metadata | _________________________________________^ 209 | | .file() 210 | | .and_then(|file| metadata.line().map(|line| (file, line))) | |__________________________________________________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.96.0/index.html#manual_option_zip = note: `-D clippy::manual-option-zip` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::manual_option_zip)]` help: use | 208 ~ if let Some((file, line)) = metadata 209 + .file().zip(metadata.line()) ``` ## Solution Apply the suggestion by Clippy and format the code (cargo fmt --all).
BatmanAoD
force-pushed
the
publish-tracing-error-to-rigetti-cargo
branch
3 times, most recently
from
0c9d75a to
58db907
Compare
Closed
BatmanAoD
force-pushed
the
publish-tracing-error-to-rigetti-cargo
branch
3 times, most recently
from
71025b9 to
1bec96b
Compare
…igetti-cargo' registry
BatmanAoD
force-pushed
the
publish-tracing-error-to-rigetti-cargo
branch
from
394dd90 to
b95a0d2
Compare
BatmanAoD
commented
Jun 16, 2026
jselig-rigetti
approved these changes
Jun 17, 2026
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
3 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.
This uses an internal GitLab mirror to run CI, including the publish step.
The first commit,
d9d4c542, is from the upstreammainbranch.To see that the new job is working, and that a prerelease is published to
rigetti-cargo: find "Trigger GitLab CI / Trigger GitLab pipeline (pull_request)" in the list of checks, then look at the log for that check and click through to the linked GitLab CI pipeline.The initial release after this is merged will not succeed, because, as part of testing this, I already published version
0.2.1to CodeArtifact. In order to publish the next version, we will need to manually bump it as part of #1 and/or #3.