Bump @biomejs/biome from 1.9.4 to 2.4.1#259
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
Bumps [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) from 1.9.4 to 2.4.1. - [Release notes](https://github.com/biomejs/biome/releases) - [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md) - [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.4.1/packages/@biomejs/biome) --- updated-dependencies: - dependency-name: "@biomejs/biome" dependency-version: 2.4.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
a team,
CarlosGamero,
drdaemos and
kibertoad
as code owners
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Development Dependency Update package.json |
Upgraded "@biomejs/biome" devDependency from "^1.9.4" to "^2.4.1" (major version bump from v1 to v2). |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
🚥 Pre-merge checks | ✅ 3 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The PR description includes comprehensive release notes and changelog details from the dependency maintainers, but lacks required template sections: no explicit 'Changes' description summary and no checklist items marked (labels, documentation/test updates). | Add a 'Changes' section summarizing the update, then complete the checklist by marking items and selecting appropriate release label (already labeled as 'major' in the PR metadata). |
✅ Passed checks (3 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title 'Bump @biomejs/biome from 1.9.4 to 2.4.1' clearly and concisely describes the main change—a dependency version upgrade—matching the single file modification in package.json. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Merge Conflict Detection | ✅ Passed | ✅ No merge conflicts detected when merging into main |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Post copyable unit tests in a comment
- Commit unit tests in branch
dependabot/npm_and_yarn/biomejs/biome-2.4.1
Comment @coderabbitai help to get the list of available commands and usage tips.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Line 48: The biome.json $schema value is still pinned to
"https://biomejs.dev/schemas/2.3.14/schema.json" which conflicts with the
package.json dependency bump to `@biomejs/biome` ^2.4.1; update the "$schema"
entry in biome.json to "https://biomejs.dev/schemas/2.4.1/schema.json" so the
schema version matches the upgraded Biome dependency and avoids
validation/linting mismatches.
| }, | ||
| "devDependencies": { | ||
| "@biomejs/biome": "^1.9.4", | ||
| "@biomejs/biome": "^2.4.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Locate Biome config files (if any)
fd -a 'biome\.(json|jsonc)$|biome\.config\.(js|cjs|mjs|ts)$'
# Quick scan for schema/version hints or extends
rg -n '"\\$schema"|schemaVersion|extends|linter|formatter' $(fd -a 'biome\.(json|jsonc)$' || true)
# Confirm lockfile update (if present)
rg -n '"@biomejs/biome"|@biomejs/biome' package-lock.json yarn.lock pnpm-lock.yaml 2>/dev/null || trueRepository: lokalise/node-core
Length of output: 145
🏁 Script executed:
#!/bin/bash
# Read the biome.json file to check structure and schema
cat -n biome.json
# Check package.json for dependencies on `@lokalise/biome-config`
echo "=== Checking for `@lokalise/biome-config` ==="
rg -n '@lokalise/biome-config' package.json
# Check lockfile for `@biomejs/biome` version
echo "=== Checking lockfile for `@biomejs/biome` ==="
if [ -f package-lock.json ]; then
echo "=== package-lock.json ==="
rg -A 5 '"@biomejs/biome"' package-lock.json | head -20
elif [ -f yarn.lock ]; then
echo "=== yarn.lock ==="
rg -A 5 '@biomejs/biome' yarn.lock | head -20
elif [ -f pnpm-lock.yaml ]; then
echo "=== pnpm-lock.yaml ==="
rg -A 5 '@biomejs/biome' pnpm-lock.yaml | head -20
fiRepository: lokalise/node-core
Length of output: 2483
🏁 Script executed:
#!/bin/bash
# Check git status/diff for biome.json to see if it's being modified
echo "=== Checking if biome.json is modified in this change ==="
git diff biome.json 2>/dev/null || echo "No git diff available"
# More detailed lockfile search
echo "=== Lockfile check ==="
if [ -f package-lock.json ]; then
echo "=== Found package-lock.json, searching for `@biomejs/biome` ==="
jq '.dependencies."@biomejs/biome"' package-lock.json 2>/dev/null || rg '"@biomejs/biome"' package-lock.json -A 3 | head -20
elif [ -f yarn.lock ]; then
echo "=== Found yarn.lock ==="
grep -A 10 '@biomejs/biome' yarn.lock | head -20
elif [ -f pnpm-lock.yaml ]; then
echo "=== Found pnpm-lock.yaml ==="
grep -A 10 '@biomejs/biome' pnpm-lock.yaml | head -20
fi
# Check what Biome 2.4.1 schema URL should be
echo "=== Schema URL for Biome 2.4.1 should be ==="
echo "https://biomejs.dev/schemas/2.4.1/schema.json"Repository: lokalise/node-core
Length of output: 2482
Update biome.json schema to match Biome 2.4.1 (Line 2 of biome.json).
The schema version in biome.json is pinned to 2.3.14, but the package.json upgrade targets ^2.4.1. Update the schema URL to https://biomejs.dev/schemas/2.4.1/schema.json to prevent validation errors and ensure the linter uses the correct rule set for version 2.4.1.
Current schema mismatch in biome.json
"$schema": "https://biomejs.dev/schemas/2.3.14/schema.json"Should be:
"$schema": "https://biomejs.dev/schemas/2.4.1/schema.json"🤖 Prompt for AI Agents
In `@package.json` at line 48, The biome.json $schema value is still pinned to
"https://biomejs.dev/schemas/2.3.14/schema.json" which conflicts with the
package.json dependency bump to `@biomejs/biome` ^2.4.1; update the "$schema"
entry in biome.json to "https://biomejs.dev/schemas/2.4.1/schema.json" so the
schema version matches the upgraded Biome dependency and avoids
validation/linting mismatches.
Contributor
Author
|
Superseded by #260. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/biomejs/biome-2.4.1
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @biomejs/biome from 1.9.4 to 2.4.1.
Release notes
Sourced from
@biomejs/biome's releases.... (truncated)
Changelog
Sourced from
@biomejs/biome's changelog.... (truncated)
Commits
5153f2fci: release (#9094)4cc531cchore: docs that break website (#9077)bf6e5f9ci: release (#9045)e014336feat: promote rules for v2.4 (#9011)7e33fd5Merge remote-tracking branch 'origin/main' into nextdf21006ci: release (#8973)6ebf6c6feat(lint): add nursery rule noUselessReturn (#9029)043b67cfeat(lint/js): addnoNestedPromises(#9019)26d8367docs: correct default value foruseEditorconfigschema setting (#9025)dc1f94efeat(assist): add noDuplicateClasses assist action (#8623)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@biomejs/biomesince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit