Skip to content

chore(lint): version released rules#7147

Merged
siketyan merged 2 commits intomainfrom
chore/version-released-rules
Aug 7, 2025
Merged

chore(lint): version released rules#7147
siketyan merged 2 commits intomainfrom
chore/version-released-rules

Conversation

@siketyan
Copy link
Copy Markdown
Member

@siketyan siketyan commented Aug 7, 2025

Summary

Replaced the version metadata in all rules released in v2.1.4.
I also updated CONTRIBUTING.md to guide this step.

Test Plan

N/A

Docs

N/A

@siketyan siketyan self-assigned this Aug 7, 2025
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Aug 7, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 9cd9d21

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
Copy Markdown
Contributor

coderabbitai Bot commented Aug 7, 2025 •
edited
Loading

Caution

Review failed

The pull request is closed.

Walkthrough

This update modifies the release process documentation and updates version metadata for several lint rules. The "Regular releases" section in CONTRIBUTING.md now includes clearer, reordered steps for preparing and executing a release, with explicit instructions to replace all "next" version strings in rule metadata with the new release version. The merge strategy for branches is clarified, and some documentation steps are removed. In the codebase, the version field for multiple nursery lint rules is changed from "next" to "v2.1.4", with no other changes to logic or functionality.

Suggested reviewers

  • ematipico

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c2c1052 and 9cd9d21.

📒 Files selected for processing (1)
  • CONTRIBUTING.md (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/version-released-rules
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 explain this code block.
  • 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 explain its main purpose.
    • @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 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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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 anywhere in the PR title to generate the title automatically.

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.

@github-actions github-actions Bot added A-Linter Area: linter L-JavaScript Language: JavaScript and super languages labels Aug 7, 2025
siketyan
siketyan commented Aug 7, 2025
View reviewed changes
Comment thread CONTRIBUTING.md
Comment on lines -473 to -477
1. [ ] Update the generated documentation in the `next` branch of the [website](https://github.com/biomejs/website):
`BIOME_VERSION=<version> pnpm run codegen:all`.
This will also copy the configuration schema in the right place.

1. [ ] Merge the website's `next` branch into `main` with a PR. Once merged, the documentation will automatically deploy.
Copy link
Copy Markdown
Member Author

@siketyan siketyan Aug 7, 2025

Choose a reason for hiding this comment

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

These steps are no longer required as they have been replaced with the automated workflow.

@siketyan siketyan force-pushed the chore/version-released-rules branch from c2c1052 to 9cd9d21 Compare August 7, 2025 16:44
@siketyan siketyan merged commit 450f63e into main Aug 7, 2025
12 of 29 checks passed
@siketyan siketyan deleted the chore/version-released-rules branch August 7, 2025 16:45
@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented Aug 7, 2025

CodSpeed Performance Report

Merging #7147 will not alter performance

Comparing chore/version-released-rules (c2c1052) with main (5666582)1

Summary

✅ 128 untouched benchmarks

Footnotes

  1. No successful run was found on main (dcaebca) during the generation of this report, so 5666582 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@ematipico
Copy link
Copy Markdown
Member

ematipico commented Aug 7, 2025

I wonder if we could have a workflow that answers to a magic comment like "update the rule version to 2.9.0" and it will commit the changes in the PR

@siketyan siketyan mentioned this pull request Aug 8, 2025
Merged
This was referenced Sep 5, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@siketyan siketyan

Labels

A-Linter Area: linter L-JavaScript Language: JavaScript and super languages

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@siketyan @ematipico