Skip to content

chore: bump wolfwave cask to v2.0.0 #6

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

Open
nathanialhenniges wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: bump wolfwave cask to v2.0.0 #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Casks/wolfwave.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
cask "wolfwave" do
version "1.2.0"
sha256 "90081458726d92441e527a12bf9716f79d0fef061d1fd651c5d176475bc04e63"
version "2.0.0"
sha256 "1141cc41194444cfca020dfde34e00ca9fcb1f1023287896b60e27d2fc9d540e"
Comment on lines +2 to +3

@coderabbitai coderabbitai Bot Jul 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Keep the generated metadata/test fixture in sync with this bump.

tests/build-output.test.js still asserts wolfwave is 1.2.0, so this change will leave the cask metadata out of sync and likely fail CI unless the downstream fixture/site output is updated in the same PR.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Casks/wolfwave.rb` around lines 2 - 3, The wolfwave cask version bump is not
reflected in the generated metadata/test fixture, so the repository will be out
of sync. Update the downstream fixture and any site/build output used by tests,
especially the wolfwave assertion in tests/build-output.test.js, to match the
new version in Casks/wolfwave.rb and keep the generated metadata consistent in
the same change.


url "https://github.com/MrDemonWolf/wolfwave/releases/download/v#{version}/WolfWave-#{version}.dmg"
name "WolfWave"
Expand Down
Loading