Skip to content

Use cargo:open - #81

Merged
jayvdb merged 1 commit into
mainfrom
add-open
Jul 13, 2026
Merged

Use cargo:open#81
jayvdb merged 1 commit into
mainfrom
add-open

Conversation

@jayvdb

@jayvdb jayvdb commented Jul 13, 2026

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Added cargo:open to the managed development tools and generated deployment configurations.
    • Added support for validating and allowing the new tool in configuration policies.
  • Bug Fixes

    • Prevented cargo:open installation on Windows environments where it is currently unsupported.
    • Updated Windows container configurations to disable the tool automatically.
  • Documentation

    • Added guidance for handling unsupported Cargo-based tools on Windows.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Adds cargo:open to mise configuration and generated deployment files, disables its installation on Windows, documents the Windows backend limitation, and updates schema and policy allowlists.

Changes

cargo:open mise integration

Layer / File(s) Summary
Register cargo:open in mise outputs
.mise/config.toml, utilities/cli/src/deployment_types/mise.rs, verification/local/output/...
Adds cargo:open = "latest" to repository and generated mise tool configurations.
Disable cargo:open on Windows
.github/actions/install-mise-tools/action.yaml, Dockerfile.nanoserver, Dockerfile.windows, CLAUDE.md
Disables cargo:open on Windows action and Docker surfaces and documents the related mise backend limitation.
Allow cargo:open in validation
config/conftest/policy/mise/mise.rego, config/taplo/mise-cargo-backend-allowlist.schema.json
Adds cargo:open to the no-prebuilt policy set and tool-name schema allowlist.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: adding and enabling the new cargo:open tool.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-open

Comment @coderabbitai help to get the list of available commands.

@deepsource-io

deepsource-io Bot commented Jul 13, 2026

Copy link
Copy Markdown

DeepSource Code Review

We reviewed changes in e199383...c51c877 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Coverage  

Code Review Summary

Analyzer Status Updated (UTC) Details
C# Jul 13, 2026 3:56a.m. Review ↗
C & C++ Jul 13, 2026 3:56a.m. Review ↗
Docker Jul 13, 2026 3:56a.m. Review ↗
Java Jul 13, 2026 3:56a.m. Review ↗
JavaScript Jul 13, 2026 3:56a.m. Review ↗
Python Jul 13, 2026 3:56a.m. Review ↗
Rust Jul 13, 2026 3:56a.m. Review ↗
Secrets Jul 13, 2026 3:56a.m. Review ↗
Code coverage Jul 13, 2026 4:19a.m. Review ↗

Code Coverage Summary

Language Line Coverage (New Code) Line Coverage (Overall)
Aggregate
100%
51.4%
[▲ up 0.1% from main]
Python -
54.2%
Rust
100%
51.3%
[▲ up 0.1% from main]

➟ Additional coverage metrics may have been reported. See full coverage report ↗


Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@codacy-production

codacy-production Bot commented Jul 13, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codecov

codecov Bot commented Jul 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@jayvdb
jayvdb marked this pull request as ready for review July 13, 2026 03:56
@jayvdb
jayvdb requested a review from pierre-tenedero July 13, 2026 03:56

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR implements the addition of cargo:open to the project configuration and supporting schemas. It correctly identifies the need to disable the tool on Windows (CI and Docker) due to installation errors. Codacy results indicate the PR is up to standards. However, a significant implementation detail in the GitHub Actions configuration needs to be addressed: the current approach for disabling tools in the CI environment overwrites existing environment variables rather than appending to them, which could lead to unintended configuration side effects in complex workflows.

About this PR

  • No PR description was provided. Including a description helps reviewers understand the context and specific rationale for the changes, especially regarding the Windows-specific exclusions.

Test suggestions

  • Verify cargo:open is correctly added to the main .mise/config.toml.
  • Verify Windows CI runners skip the installation of cargo:open.
  • Verify Windows Docker images (NanoServer/Standard) have cargo:open in their disable list.
  • Verify the mise configuration generator produces a mise.toml containing cargo:open.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread .github/actions/install-mise-tools/action.yaml

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/actions/install-mise-tools/action.yaml:
- Around line 31-34: Update the Windows step that sets MISE_DISABLE_TOOLS to
preserve any existing comma-separated value while appending cargo:open. Read the
current environment value, append cargo:open with the appropriate separator, and
write the combined list to GITHUB_ENV instead of overwriting the caller-provided
disable list.

In `@Dockerfile.windows`:
- Around line 161-162: Move the cargo:open entry from the child build stage’s
MISE_DISABLE_TOOLS declaration into the build-minimal stage before its first
mise install. Keep the dotnet:roslynator.dotnet.cli and pipx:torch entries in
the child build stage’s environment configuration.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5342d0b6-f829-41ae-83e9-b7e9369bf3eb

📥 Commits

Reviewing files that changed from the base of the PR and between e199383 and c51c877.

📒 Files selected for processing (9)
  • .github/actions/install-mise-tools/action.yaml
  • .mise/config.toml
  • CLAUDE.md
  • Dockerfile.nanoserver
  • Dockerfile.windows
  • config/conftest/policy/mise/mise.rego
  • config/taplo/mise-cargo-backend-allowlist.schema.json
  • utilities/cli/src/deployment_types/mise.rs
  • verification/local/output/facility-security-scenario/mise.toml

Comment thread .github/actions/install-mise-tools/action.yaml
Comment thread Dockerfile.windows
@jayvdb
jayvdb requested a review from Zoybean July 13, 2026 04:47
@jayvdb
jayvdb merged commit bd0eecb into main Jul 13, 2026
50 checks passed
@jayvdb
jayvdb deleted the add-open branch July 13, 2026 06:15
@coderabbitai coderabbitai Bot mentioned this pull request Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants