Skip to content

droppy@beta 15.0.0-beta.4 - #283386

Open
droppyformac wants to merge 1 commit into
Homebrew:mainfrom
droppyformac:droppy@beta-15.0.0-beta.4
Open

droppy@beta 15.0.0-beta.4#283386
droppyformac wants to merge 1 commit into
Homebrew:mainfrom
droppyformac:droppy@beta-15.0.0-beta.4

Conversation

@droppyformac

Copy link
Copy Markdown

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 <cask> worked successfully.
  • HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
  • brew uninstall --cask <cask> worked successfully.

  • I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output, including zap stanza paths; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

Droppy is released in beta channels; the current stable line (14.2.0) is superseded by 15.0.0 pre-releases on the vendor's recommended channel. This cask uses the alternative-release-channel token per the Acceptable Casks policy, pointing at the vendor's public, versioned beta DMG path, verified by SHA-256 (6986518f56cb9fefd850d3dd6178f1872405c051468e26535400c43650bc64b8) against the release manifest at https://droppy-releases.jordylegrand.workers.dev/app-releases/beta/latest.json.

The install/uninstall cycle was verified with brew audit --new, brew audit --online and brew style in a test tap on the maintainer's machine, but the actual install+uninstall round-trip was skipped locally because the machine's /Applications/Droppy.app currently carries another release channel and was not overwritten; the CI cask checks will cover it.

AI/LLM disclosure: this PR was assisted by an LLM (DeepSeek-V4-Flash-Vision model via the opencode agent). Drafting was done by the developer, who reviewed the generated cask stanza-by-stanza, confirmed the checksum by downloading the DMG directly and comparing it with the release manifest, and ran the audits and style checks shown above. No AI attribution on commits; all maintainer review responses will be authored by the developer.

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.

2 participants