Skip to content

chore(main): release 0.21.2 - #216

Merged
AyushSehrawat merged 1 commit into
mainfrom
release-please--branches--main
Aug 17, 2025
Merged

chore(main): release 0.21.2#216
AyushSehrawat merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@dreulavelle

@dreulavelle dreulavelle commented Aug 17, 2025

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

0.21.2 (2025-08-17)

Bug Fixes

  • don't json parse oldLogs (1a00ffa)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue with older logs being incorrectly parsed as JSON, improving reliability when viewing or processing historical logs.
  • Documentation

    • Updated CHANGELOG with release 0.21.2 details.
  • Chores

    • Bumped version to 0.21.2.

@coderabbitai

coderabbitai Bot commented Aug 17, 2025

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Adds a new 0.21.2 patch entry to CHANGELOG.md noting a bug fix (“don’t json parse oldLogs”) and bumps version.txt from 0.21.1 to 0.21.2. No code or API changes are included.

Changes

Cohort / File(s) Summary of Changes
Release notes
CHANGELOG.md
Added 0.21.2 entry dated 2025-08-17 with a bug fix reference.
Versioning
version.txt
Bumped version from 0.21.1 to 0.21.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

autorelease: tagged

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-please--branches--main

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
🪧 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 coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1a00ffa and 52bf57e.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • version.txt (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[grammar] ~3-~3: Use correct spacing
Context: .../compare/v0.21.1...v0.21.2) (2025-08-17) ### Bug Fixes * don't json parse oldLogs ([...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~6-~6: Use correct spacing
Context: ......v0.21.2) (2025-08-17) ### Bug Fixes * don't json parse oldLogs ([1a00ffa](http...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~8-~8: There might be a mistake here.
Context: ...00ffa3355002beb245aac23718648fb4de04d5)) ## [0.21.1](https://github.com/rivenmedia/ri...

(QB_NEW_EN_OTHER)

🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

5-5: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

🔇 Additional comments (1)
version.txt (1)

1-1: Version bump looks correct and aligned with changelog

Matches CHANGELOG entry 0.21.2 and PR metadata. Nothing else to do.

Comment thread CHANGELOG.md
Comment on lines +4 to +5


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove extra blank line to satisfy markdownlint (MD012)

There are two consecutive blank lines before “### Bug Fixes”, which violates MD012 and may fail linting.

Apply this diff:

 ## [0.21.2](https://github.com/rivenmedia/riven-frontend/compare/v0.21.1...v0.21.2) (2025-08-17)
-
 
 ### Bug Fixes
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## [0.21.2](https://github.com/rivenmedia/riven-frontend/compare/v0.21.1...v0.21.2) (2025-08-17)
### Bug Fixes
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

5-5: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

🤖 Prompt for AI Agents
In CHANGELOG.md around lines 4 to 5 there are two consecutive blank lines before
the "### Bug Fixes" header which violates markdownlint rule MD012; open the file
and remove the extra blank line so only a single blank line separates the
previous content and the "### Bug Fixes" header, then save the file to resolve
the lint error.

Comment thread CHANGELOG.md

### Bug Fixes

* don't json parse oldLogs ([1a00ffa](https://github.com/rivenmedia/riven-frontend/commit/1a00ffa3355002beb245aac23718648fb4de04d5))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Nit: capitalize and hyphenate “JSON-parse” for clarity

Optional copyedit for consistency with common style guides.

-* don't json parse oldLogs ([1a00ffa](https://github.com/rivenmedia/riven-frontend/commit/1a00ffa3355002beb245aac23718648fb4de04d5))
+* don't JSON-parse oldLogs ([1a00ffa](https://github.com/rivenmedia/riven-frontend/commit/1a00ffa3355002beb245aac23718648fb4de04d5))
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* don't json parse oldLogs ([1a00ffa](https://github.com/rivenmedia/riven-frontend/commit/1a00ffa3355002beb245aac23718648fb4de04d5))
* don't JSON-parse oldLogs ([1a00ffa](https://github.com/rivenmedia/riven-frontend/commit/1a00ffa3355002beb245aac23718648fb4de04d5))
🧰 Tools
🪛 LanguageTool

[grammar] ~8-~8: There might be a mistake here.
Context: ...00ffa3355002beb245aac23718648fb4de04d5)) ## [0.21.1](https://github.com/rivenmedia/ri...

(QB_NEW_EN_OTHER)

🤖 Prompt for AI Agents
In CHANGELOG.md around line 8, the entry uses "json parse" in lowercase and
without a hyphen; update it to "JSON-parse" (capitalize JSON and add the hyphen)
so the line reads: "* don't JSON-parse oldLogs (...)" to match style and
clarity.

@AyushSehrawat
AyushSehrawat merged commit 39819e7 into main Aug 17, 2025
4 of 6 checks passed
@AyushSehrawat
AyushSehrawat deleted the release-please--branches--main branch August 17, 2025 18:42
@dreulavelle

Copy link
Copy Markdown
Member Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants