Skip to content

cleanup: don't warn when loading a renamed cask. #20256

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 15, 2025
Merged

cleanup: don't warn when loading a renamed cask. #20256

merged 1 commit into from
Jul 15, 2025

Conversation

MikeMcQuaid
Copy link
Member

Fixes #20248

@MikeMcQuaid MikeMcQuaid enabled auto-merge July 15, 2025 11:10
EricFromCanada
EricFromCanada reviewed Jul 15, 2025
View reviewed changes
@MikeMcQuaid MikeMcQuaid force-pushed the renamed_cask_no_warn branch from ccbec46 to dd3c6a6 Compare July 15, 2025 13:22
@MikeMcQuaid MikeMcQuaid added this pull request to the merge queue Jul 15, 2025
Merged via the queue into main with commit 39b3d3d Jul 15, 2025
36 checks passed
@MikeMcQuaid MikeMcQuaid deleted the renamed_cask_no_warn branch July 15, 2025 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@p-linnane p-linnane p-linnane approved these changes

@EricFromCanada EricFromCanada Awaiting requested review from EricFromCanada

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Confusing warning caused by caches of renamed cask
3 participants
@MikeMcQuaid @EricFromCanada @p-linnane