Skip to content

cargo-shuttle: fix test #221578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 27, 2025
Merged

cargo-shuttle: fix test #221578

merged 1 commit into from
Apr 27, 2025

Conversation

daeho-ro
Copy link
Member

It seems that the api response is changed, so have to fix the test.


  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

@github-actions github-actions bot added the rust Rust use is a significant feature of the PR or issue label Apr 27, 2025
@stefanb stefanb added the CI-no-bottles Merge without publishing bottles label Apr 27, 2025
@BrewTestBot BrewTestBot added this pull request to the merge queue Apr 27, 2025
Merged via the queue into master with commit 8c1e244 Apr 27, 2025
25 checks passed
@BrewTestBot BrewTestBot deleted the fix-test-carto-shuttle branch April 27, 2025 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI-no-bottles Merge without publishing bottles rust Rust use is a significant feature of the PR or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants