chore: bump wolfwave cask to v2.0.0

[nathanialhenniges]

Automated cask update for WolfWave v2.0.0.

• Version: 2.0.0
• SHA256 updated from released DMG

Triggered by wolfwave release v2.0.0.

Summary by CodeRabbit

• Chores
  • Updated the app’s package metadata to version 2.0.0.
  • Refreshed the download checksum to match the latest release artifact.

[coderabbitai]

Walkthrough

Updated the wolfwave cask's version field from 1.2.0 to 2.0.0 and replaced the corresponding sha256 checksum to match the new release artifact.

Changes

Wolfwave Cask Update

Layer / File(s)	Summary
Version and checksum bump Casks/wolfwave.rb	Updates the cask version to 2.0.0 and replaces the sha256 checksum for the new release artifact.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• MrDemonWolf/homebrew-den#4: Same file update pattern — bumps the wolfwave cask version and sha256 checksum for a prior release.

Poem

A hop, a skip, a version bump,
WolfWave grows from a tiny lump,
New sha256, shiny and bright,
2.0.0 hops into the light! 🐰✨
Carrots for checksums, my work here is done!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the WolfWave cask to version 2.0.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wolfwave-v2.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with 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.

Inline comments:
In `@Casks/wolfwave.rb`:
- Around line 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.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 00b065e6-32c9-465b-8aea-167ba5222a4f

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd44bf and 70c51b3.

📒 Files selected for processing (1)

• Casks/wolfwave.rb

[coderabbitai]

🎯 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.