chore: update dependencies and license link

[shuhuiluo]

• Bumped @openzeppelin/contracts, forge-std, and solady dependencies to latest versions.
• Updated MIT license badge link in README.md to direct to the project's LICENSE file.
• Incremented version to 0.6.2.

Summary by CodeRabbit

• Documentation

  • Updated README license badge to link directly to the repository’s LICENSE file for clearer attribution. No functional changes.

• Chores

  • Bumped version to 0.6.2.
  • Updated dependencies to align with latest ecosystem releases:
    • OpenZeppelin Contracts to ^5.4.0
    • forge-std to v1.10.0
    • solady to ^0.1.24
  • These updates improve compatibility and maintenance without impacting existing behavior.

[coderabbitai]

Walkthrough

This PR updates the README license badge link to point to the repository LICENSE file and bumps package.json from 0.6.1 to 0.6.2, updating dependency versions for @openzeppelin/contracts, forge-std, and solady. No code or API changes.

Changes

Cohort / File(s)	Summary of Changes
Documentation README.md	Updated MIT badge/link target from opensource.org to repo LICENSE file.
Release and Dependencies package.json	Bumped version 0.6.1 → 0.6.2. Updated deps: @openzeppelin/contracts ^5.3.0 → ^5.4.0, forge-std v1.9.7 → v1.10.0, solady ^0.1.14 → ^0.1.24.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Release Towns Protocol Diamond 3efcb17 #71: Previous version bump (0.6.0 → 0.6.1) closely precedes this release increment.
• Release Towns Protocol Diamond 5b77aa8 #66: Release-related package.json updates similar in scope.
• Release Towns Protocol Diamond 9ac7457 #61: Another package.json version change aligned with release workflow.

Poem

A nibble of text, a hop in the tag,
The badge now points where licenses wag.
Version ticks up—soft thump of a paw,
Dependencies fresh, as carrots in straw.
I stamp, I merge, I scamper away—
0.6.2 is live today! 🥕🐇

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch shuhui/dep

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

5-5: Use a relative link to LICENSE for better portability across forks/branches

Linking directly to the repo URL works, but a relative link keeps the badge target valid in forks and when the default branch changes.

Apply this diff:

-[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/towns-protocol/diamond/blob/main/LICENSE)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 243054b and 2d26430.

📒 Files selected for processing (2)

• README.md (1 hunks)
• package.json (2 hunks)

🔇 Additional comments (2)

package.json (2)

3-3: Version bump to 0.6.2 looks good

No issues spotted with the package metadata update.

---

41-45: Import Paths Remappings Verified; Manual Test & Lockfile Check Needed

All import paths for OpenZeppelin, Solady, and forge-std remain unchanged after bumping to:

• @openzeppelin/contracts ^5.4.0
• solady ^0.1.24
• forge-std github:foundry-rs/forge-std#v1.10.0

Next steps before release:

• Re-run forge build && forge test locally to confirm nothing breaks.
• Ensure your lockfile (package-lock.json, yarn.lock, etc.) is updated to reflect these dependency versions for reproducibility.