Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@WuMingDao
Copy link
Contributor

Summary

Test Plan

Docs

@changeset-bot
Copy link

changeset-bot bot commented Nov 5, 2025

⚠️ No Changeset found

Latest commit: ab9a0c6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 5, 2025

Walkthrough

This PR updates RELEASES.md with several grammatical and wording corrections: changes “enforcing deadlines to a group of volunteers” → “enforcing deadlines for a group of volunteers”; “they are meant for testing and verify that bugs are fixed” → “they are meant for testing and verifying that bugs are fixed”; fixes “rights” → “right” in Beta and Stable release sections; and simplifies “one single version” → “a single version”. No code or API surface changes.

Suggested reviewers

  • dyc3

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description contains only template boilerplate with empty sections and no substantive content about the actual changes or motivation. Fill in the Summary section with motivation for these grammar fixes, and consider whether a changeset is needed for documentation changes.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarises the main change: grammar and typo corrections in RELEASES.md, matching the file-level summaries provided.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1e7db7 and ab9a0c6.

📒 Files selected for processing (1)
  • RELEASES.md (3 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-10-15T09:24:31.042Z
Learnt from: CR
Repo: biomejs/biome PR: 0
File: crates/biome_parser/CONTRIBUTING.md:0-0
Timestamp: 2025-10-15T09:24:31.042Z
Learning: Applies to crates/biome_parser/crates/biome_*_{syntax,factory}/** : Create per-language crates biome_<lang>_syntax and biome_<lang>_factory under crates/

Applied to files:

  • RELEASES.md
📚 Learning: 2025-10-15T09:22:46.002Z
Learnt from: CR
Repo: biomejs/biome PR: 0
File: crates/biome_js_formatter/CONTRIBUTING.md:0-0
Timestamp: 2025-10-15T09:22:46.002Z
Learning: Applies to crates/biome_js_formatter/**/Cargo.toml : Declare the dependency `biome_js_formatter = { version = "0.0.1", path = "../biome_js_formatter" }` for internal installation

Applied to files:

  • RELEASES.md
🪛 LanguageTool
RELEASES.md

[style] ~5-~5: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...olunteers is counterproductive, and can have negative effects on people. ## npm packages ### Prerele...

(ADVERSE_EFFECT_ON)


[uncategorized] ~11-~11: Do not mix variants of the same word (‘pre-release’ and ‘prerelease’) within a single text.
Context: ...mpackages ### Prerelease We publish pre-releases of the main@biomejs/biome` package tw...

(EN_WORD_COHERENCY)

🔇 Additional comments (5)
RELEASES.md (5)

5-5: Preposition fix is correct.

Changing "to a group" to "for a group" is the right idiom here. ✓


11-11: Gerund form is correct, but note an existing terminology inconsistency.

The change from "verify" to "verifying" is grammatically sound. However, this line contains "pre-releases" (hyphenated, lowercase) while the section heading above uses "Prerelease" (non-hyphenated). This inconsistency predates this PR, but you may want to flag it with maintainers for a future consistency pass across the documentation.


20-20: Singular "right" is correct.

The idiom is "the right to [do something]", not "rights". ✓


28-28: Excellent—fixes the copy-paste error flagged in the previous review.

Line 28 now correctly reads "Stable releases" instead of "Beta releases" to match the section heading. Well done addressing the earlier feedback.


40-40: Removes unnecessary redundancy.

"One single version" → "a single version" is clearer and more concise. ✓


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
RELEASES.md (1)

11-11: Terminology inconsistency: Consider standardising hyphenation.

The section heading uses "Prerelease" (no hyphen) whilst line 11 uses "pre-releases" (hyphenated). Choose one variant consistently throughout the document.

Static analysis also flags this. If you prefer the non-hyphenated form:

-We publish pre-releases of the main `@biomejs/biome` package twice a week.
+We publish prerelease versions of the main `@biomejs/biome` package twice a week.
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0b28f5f and c1e7db7.

📒 Files selected for processing (1)
  • RELEASES.md (3 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-10-15T09:24:31.042Z
Learnt from: CR
Repo: biomejs/biome PR: 0
File: crates/biome_parser/CONTRIBUTING.md:0-0
Timestamp: 2025-10-15T09:24:31.042Z
Learning: Applies to crates/biome_parser/crates/biome_*_{syntax,factory}/** : Create per-language crates biome_<lang>_syntax and biome_<lang>_factory under crates/

Applied to files:

  • RELEASES.md
📚 Learning: 2025-10-15T09:22:46.002Z
Learnt from: CR
Repo: biomejs/biome PR: 0
File: crates/biome_js_formatter/CONTRIBUTING.md:0-0
Timestamp: 2025-10-15T09:22:46.002Z
Learning: Applies to crates/biome_js_formatter/**/Cargo.toml : Declare the dependency `biome_js_formatter = { version = "0.0.1", path = "../biome_js_formatter" }` for internal installation

Applied to files:

  • RELEASES.md
🪛 LanguageTool
RELEASES.md

[style] ~5-~5: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...olunteers is counterproductive, and can have negative effects on people. ## npm packages ### Prerele...

(ADVERSE_EFFECT_ON)


[uncategorized] ~11-~11: Do not mix variants of the same word (‘pre-release’ and ‘prerelease’) within a single text.
Context: ...mpackages ### Prerelease We publish pre-releases of the main@biomejs/biome` package tw...

(EN_WORD_COHERENCY)

🔇 Additional comments (1)
RELEASES.md (1)

5-5: Grammatical corrections look good. The preposition fix (deadlines for vs to), parallel verb form (verifying), and redundancy removal (a single vs one single) all improve clarity and consistency.

Also applies to: 11-11, 40-40

@ematipico ematipico merged commit e8f930b into biomejs:main Nov 5, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants