Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

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


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.

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


## [0.21.1](https://github.com/rivenmedia/riven-frontend/compare/v0.21.0...v0.21.1) (2025-08-15)


Expand Down
2 changes: 1 addition & 1 deletion version.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.21.1
0.21.2
Loading