Skip to content

clearly 1.6.0 (new cask)#255459

Open
alionar wants to merge 2 commits intoHomebrew:mainfrom
alionar:feat-cask-clearly
Open

clearly 1.6.0 (new cask)#255459
alionar wants to merge 2 commits intoHomebrew:mainfrom
alionar:feat-cask-clearly

Conversation

@alionar
Copy link
Contributor

@alionar alionar commented Mar 23, 2026


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

Additionally, if adding a new cask:

  • Named the cask according to the token reference.
  • Checked the cask was not already refused (add your cask's name to the end of the search field).
  • brew audit --cask --new clearly worked successfully.
    • NOTE: audit passes with one warning about the GitHub repository being less than 30 days old. Submitting for review and happy to wait for merge until notability requirements are met.
  • HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask clearly worked successfully.
  • brew uninstall --cask clearly worked successfully.

  • AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes, including zap stanza paths.
    • Claude Code (claude-sonnet-4-6) generated the initial cask structure and stanzas (desc, livecheck, depends_on, app), suggested the verified: fix for the URL stanza, and advised on commit message format based on commit history.
    • DeepWiki queried the repository's project.yml to get the bundle ID (com.sabotage.clearly) and minimum macOS version (14.0).
    • I ran brew generate-zap clearly after installing and launching the app to replace the AI-generated zap paths, then ran brew style --fix clearly to correct the glob pattern.
    • Claude Code also helped interpret audit errors and style violations throughout the process.

@alionar alionar force-pushed the feat-cask-clearly branch from 688a1e2 to af7c664 Compare March 23, 2026 13:05
@alionar alionar changed the title clearly 1.5.0 (new cask) clearly 1.6.0 (new cask) Mar 23, 2026
@alionar alionar force-pushed the feat-cask-clearly branch from af7c664 to cb11afa Compare March 23, 2026 13:08
Comment on lines +10 to +14

livecheck do
url :url
strategy :github_latest
end
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
livecheck do
url :url
strategy :github_latest
end

The default livecheck should suffice here.
Although I am concerned about the release cadence, if it continues at the current rate it will likely need to be throttled in Homebrew if there are multiple releases per day.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

release cadence

Noted. The app is newly released and the developer is iterating quickly. I'll keep an eye on the release cadence.

url "https://github.com/Shpigford/clearly/releases/download/v#{version}/Clearly.dmg",
verified: "github.com/Shpigford/clearly/"
name "Clearly"
desc "Clean, native markdown editor"
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
desc "Clean, native markdown editor"
desc "Markdown editor"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

Copy link
Member

@bevanjkay bevanjkay left a comment

Choose a reason for hiding this comment

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

It likely also requires an auto_updates stanza at it seems to have an in-app auto-update mechanism

@alionar
Copy link
Contributor Author

alionar commented Mar 23, 2026

It likely also requires an auto_updates stanza at it seems to have an in-app auto-update mechanism

Added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants