motion 0.61.0 (new cask)

[nihaals]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• [x] The submission is for a stable version or documented exception.
• [ ] brew audit --cask --online <cask> is error-free.
• [x] brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• [x] Named the cask according to the token reference.
• [ ] Checked the cask was not already refused.
• [x] Checked the cask is submitted to the correct repo.
• [ ] brew audit --cask --new <cask> worked successfully.
• [x] HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• [x] brew uninstall --cask <cask> worked successfully.

[nihaals]

I thought :github_releases already checked for the release marked latest but it seems it's picking up on the release created later instead. I tried searching the repo for examples but all the examples I could find were for skipping pre-releases so I'm not sure what the neatest way of finding the release is. See the release for more context.

Also the repo isn't notable as it's a releases-only repo that isn't linked to other than directly to assets.

[SMillerDev]

I thought :github_releases already checked for the release marked latest but it seems it's picking up on the release created later instead. I tried searching the repo for examples but all the examples I could find were for skipping pre-releases so I'm not sure what the neatest way of finding the release is. See the release for more context.

That's :github_latest, releases just checks for the most recent release.

[miccal]

/rebase

[bevanjkay]

Thank you @nihaals