feat: treasury report march

[kemuru]

Summary by CodeRabbit

• New Features
  • Expanded treasury reports by including the March 2025 report, enabling users to access the updated information.

[coderabbitai]

Walkthrough

A new entry for March 2025 has been added to the MONTHS array in the src/pages/treasury.js file. This entry includes the properties month ("March"), year ("2025"), and a treasuryReport URL pointing to the corresponding report. The update expands the set of available treasury reports without modifying any exported or public declarations.

Changes

File(s)	Change Summary
src/pages/treasury.js	Added a new entry for March 2025 (properties: month, year, treasuryReport) to the MONTHS array.

Possibly related PRs

• chore: automate latest month and year calculation #305: Adds new logic for selecting treasury reports by updating the MONTHS array.
• feat: add treasury reports december 2024 #302: Introduces an entry for December 2024 in the MONTHS array, involving similar modifications.
• feat: treasury report february #306: Inserts an entry for February 2025 into the MONTHS array, aligning closely with this update.

Suggested reviewers

• alcercu
• jaybuidl

Poem

I hopped through lines of code today,
Adding March 2025 along the way.
Treasury tales now shine so bright,
A springtime report in clear sight.
With whiskers twitching and spirits high,
I code with a joyful, bouncy sigh!
🐇💻

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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 or @coderabbitai title 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

Documentation and Community

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/pages/treasury.js (1)

13-13: Consider standardizing the naming pattern for consistency.

The PDF filename "march-2025-tr.pdf" uses a slightly different naming pattern compared to other recent months like "february-2025.pdf" or "treasury-january-2025.pdf". While this won't affect functionality, maintaining a consistent naming convention improves maintainability.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 541d23a and 56a961e.

📒 Files selected for processing (1)

• src/pages/treasury.js (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - kleros-website
• GitHub Check: Header rules - kleros-website
• GitHub Check: Pages changed - kleros-website

🔇 Additional comments (2)

src/pages/treasury.js (2)

10-14: The March 2025 treasury report entry looks good.

The new entry correctly maintains the chronological order in the MONTHS array, with the most recent month (March 2025) placed at the top. The entry follows the expected structure with all required properties.

---

10-14: Note: No risk report included for March 2025.

Unlike some other months that include both treasury and risk reports, this entry only includes a treasury report. If a risk report for March 2025 is available or will be available soon, consider adding it.