ci: release #6418
Merged
ci: release #6418
Conversation
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
github-actions
bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
d758139 to
57c5dfb
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
57c5dfb to
c3743a2
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@biomejs/[email protected]
Patch Changes
#6425
00e97adThanks @siketyan! - Fixed #6391: the rulenoUselessFragmentsno longer reports a fragment that contains whitespaces which aren't trimmed by the runtime.#6417
dd88565Thanks @ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported bynoUnknownPseudoClassornoUnknownPseudoElementrules.:open::details-content::prefix::search-text::suffix#6417
dd88565Thanks @ematipico! - Fixed #6357, where the boolean values weren't correctly merged when using theextendsfunctionality. Now Biome correctly merges the values.#6417
dd88565Thanks @ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tagsnbandnn.#6385
94142ddThanks @siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.#6417
dd88565Thanks @ematipico! - Fixed #6278:useExhaustiveDependenciesno longer adds duplicated dependencies into the list.#6417
dd88565Thanks @ematipico! - Fix 💅lint/correctness/useHookAtTopLevel: Reportingvi.useFakeTimers()#6396, wherevi.useFakeTimers()andvi.useRealTimers()incorrectly triggered React Hooks-related rules#6417
dd88565Thanks @ematipico! - Fixed a bug where Biome didn't correctly discover nested configuration files when using thelintcommand and the linter is disabled in the root configuration.#6422
594ec50Thanks @ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.#6388
c6942d2Thanks @siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]