Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(package): update @biomejs/biome to version 1.9.2 #792

Merged
merged 1 commit into from
Sep 20, 2024

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Sep 20, 2024

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​biomejs/biome (1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-darwin-arm64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-darwin-x64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-linux-arm64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-linux-arm64-musl (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-linux-x64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-linux-x64-musl (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-win32-arm64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.

↗️ @​biomejs/cli-win32-x64 (indirect, 1.9.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2 (from changelog)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Sep 20, 2024
@depfu depfu bot merged commit b3f76fb into main Sep 20, 2024
8 checks passed
@depfu depfu bot deleted the depfu/update/npm/@biomejs/biome-1.9.2 branch September 20, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants