Skip to content
New issue

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

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

Already on GitHub? # to your account

imazing 3.1.1 #204114

Merged
merged 1 commit into from
Mar 7, 2025
Merged

imazing 3.1.1 #204114

merged 1 commit into from
Mar 7, 2025

Conversation

BrewTestBot
Copy link
Member

Created by brew bump


Created with brew bump-cask-pr.

@BrewTestBot BrewTestBot added the bump-cask-pr PR was created using `brew bump-cask-pr` label Mar 6, 2025
@samford samford force-pushed the bump-imazing-3.1.1-21292 branch from 502cae5 to c828e6c Compare March 6, 2025 19:03
Copy link
Member

@samford samford left a comment

Choose a reason for hiding this comment

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

This PR was originally for 3.1.1,21292 but 3.1.1,21294 was released between then and now, so I updated this to the latter.

Edit: There must be some caching involved somewhere, as 3.1.1,21292 is still reported as newest version on CI.

@bevanjkay bevanjkay enabled auto-merge March 6, 2025 22:21
@khipp khipp force-pushed the bump-imazing-3.1.1-21292 branch 2 times, most recently from c889945 to cdd5910 Compare March 7, 2025 10:09
@samford samford force-pushed the bump-imazing-3.1.1-21292 branch from cdd5910 to c404c47 Compare March 7, 2025 13:25
@samford
Copy link
Member

samford commented Mar 7, 2025

It doesn't look like this is going to resolve itself anytime soon, so I restored the original 3.1.1,21292 version bump commit.

@bevanjkay bevanjkay merged commit 499ab43 into master Mar 7, 2025
11 checks passed
@bevanjkay bevanjkay deleted the bump-imazing-3.1.1-21292 branch March 7, 2025 13:52
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bump-cask-pr PR was created using `brew bump-cask-pr`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants