-
Notifications
You must be signed in to change notification settings - Fork 0
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(deps): update all non-major dependencies #90
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+862
−1,003
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 4, 2024 20:25
1a580c5
to
dc45e2a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 5, 2024 15:56
dc45e2a
to
785adb7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 5, 2024 19:02
785adb7
to
35d264f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 6, 2024 00:05
35d264f
to
9898273
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 6, 2024 09:24
9898273
to
b13c949
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 6, 2024 20:36
b13c949
to
86cfc63
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 7, 2024 01:36
86cfc63
to
47be342
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 7, 2024 06:54
47be342
to
3271395
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 7, 2024 16:32
3271395
to
9f30e37
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 8, 2024 08:45
9f30e37
to
a472a6c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 8, 2024 17:16
a472a6c
to
7f68364
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 9, 2024 17:08
7f68364
to
e487931
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 9, 2024 17:36
e487931
to
4af51af
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 9, 2024 20:30
4af51af
to
97c8852
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
September 12, 2024 23:11
7d21fbd
to
1f30c15
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
19 times, most recently
from
September 19, 2024 19:30
6aee1eb
to
2492a3a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 20, 2024 12:02
2492a3a
to
6156413
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 20, 2024 20:23
6156413
to
21e1b89
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
1.8.3
->1.9.2
2.2.231
->2.2.251
1.0.7
->1.1.0
1.45.3
->1.47.2
0.0.22
->0.0.25
5.2.0
->5.2.3
2.5.18
->2.5.28
3.1.1
->3.1.2
22.0.0
->22.5.5
6.4.15
->6.4.16
18.3.3
->18.3.8
7.17.0
->7.18.0
7.17.0
->7.18.0
2.0.1
->2.0.3
1.33.0
->1.34.0
10.4.19
->10.4.20
0.21.12
->0.21.15
0.23.0
->0.24.2
0.32.1
->0.33.0
0.32.1
->0.33.0
8.57.0
->8.57.1
2.43.0
->2.44.0
20.16.0-alpine
->20.17.0-alpine
6.9.14
->6.9.15
8.12.0
->8.13.0
9.3.2
->9.4.0
9.6.0
->9.11.0
8.4.40
->8.4.47
3.8.4
->3.8.6
2.16.1
->2.19.0
2.16.1
->2.19.0
2.4.0
->2.5.2
3.4.7
->3.4.12
2.0.9
->2.1.2
5.5.4
->5.6.2
0.19.0
->0.19.3
2.0.4
->2.1.1
Release Notes
biomejs/biome (@biomejs/biome)
v1.9.2
Compare Source
CLI
New features
Added support for custom GritQL definitions, including:
Contributed by @arendjr
Bug fixes
contains
queries to report false positives when the matchednode 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
andsource.fixAll.biome
.Now, if you enable
organizeImports.enabled: true
in thebiome.json
, and then you configure your editor with the following code actionsource.organizeImports.biome: false
, the editor won't sort the imports.Contributed by @ematipico
Linter
New features
Bug fixes
noLabelWithoutControl now accept JSX expression as label value (#3875). Contributed by @Conaclos
useFilenamingConvention no longer suggests names with a disallowed case (#3952). Contributed by @Conaclos
useFilenamingConvention now recognizes file names starting with ASCII digits as lowercase (#3952).
Thus,
2024-09-17-filename
,2024_09_17_filename
and20240917FileName
are inkebab-case
,snake_case
, andcamelCase
respectively.Contributed by @Conaclos
useFilenamingConvention now applies the configured formats to the file extensions (#3650). Contributed by @Conaclos
Parser
Bug fixes
useStrictMode now reports Script files with some directives, but without the
use strict
directive. Contributed by @ConaclosThe CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos
v1.9.1
Compare Source
Analyzer
CLI
Bug fixes
useEditorConfig
now loads the editorconfig when runningbiome ci
#3864. Contributed by @dyc3Revert #3731 to fix broken quick fixes and code actions. Contributed by @nhedger
Configuration
Editors
Formatter
JavaScript APIs
Linter
New Features
Bug fixes
useSemanticElements now ignores
alert
andalertdialog
roles (3858). Contributed by @ConaclosnoUndeclaredDependencies now ignores
@/
imports and recognizes type imports from Definitely Typed andbun
imports. Contributed by @ConaclosParser
v1.9.0
Compare Source
Analyzer
CLI
New features
Add
--graphql-linter-enabled
option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipicoNew EXPERIMENTAL
search
command. The search command allows you to search a Biome project using GritQL syntax.GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.
While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.
For now, the
search
command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.
Contributed by @arendjr and @BackupMiles
The option
--max-diagnostics
now accept anone
value, which lifts the limit of diagnostics shown. Contributed by @ematipicoAdd a new reporter
--reporter=gitlab
, that emits diagnostics for using the GitLab Code Quality report.Contributed by @NiclasvanEyk
Add new options to the
lsp-proxy
andstart
commands:--log-path
: a directory where to store the daemon logs. The commands also accepts the environment variableBIOME_LOG_PATH
.--log-prefix-name
: a prefix that's added to the file name of the logs. It defaults toserver.log
. The commands also accepts the environment variableBIOME_LOG_PREFIX_NAME
.@Contributed by @ematipico
Enhancements
When a
--reporter
is provided, and it's different from the default one, the value provided by via--max-diagnostics
is ignored and the limit is lifted. Contributed by @ematipicobiome init
now generates a new config file with more options set.This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by @Conaclos
The
--verbose
flag now reports the list of files that were evaluated, and the list of files that were fixed.The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.
Contributed by @ematipico
Allow passing
nursery
to the--only
and--skip
filters.The
--only
option allows you to run a given rule or rule group.The
--skip
option allows you to skip the execution of a given group or a given rule.Previously, it was not possible to pass
nursery
.This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.
Contributed by @Conaclos
The CLI now returns an error code when calling a command in
stdin
mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of1
because thelint
command triggers some lint rules:Contributed by @ematipico
Bug fixes
biome lint --write
now takes--only
and--skip
into account (#3470). Contributed by @ConaclosFix #3368, now the reporter
github
tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipicoFix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219
Migrating from Prettier or ESLint no longer overwrite the
overrides
field from the configuration (#3544). Contributed by @ConaclosFix JSX expressions for
noAriaHiddenOnFocusable
(#3708). Contributed by @anthonyshewFix edge case for
<canvas>
elements that userole="img"
(#3728). Contributed by @anthonyshewFix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow
aria-label
on heading to preventuseHeadingContent
diagnostic (#3767). Contributed by @anthonyshewFix edge case #3791 for rule
noFocusedTests
being used with non-string-like expressions (#3793). Contributed by @h-a-n-aFix optional ARIA properties for
role="separator"
inuseAriaPropsForRole
(#3856). Contributed by @anthonyshewConfiguration
Add support for loading configuration from
.editorconfig
files (#1724).Configuration supplied in
.editorconfig
will be overridden by the configuration inbiome.json
. Support is disabled by default and can be enabled by adding the following to your formatter configuration inbiome.json
:Contributed by @dyc3
overrides
from an extended configuration is now merged with theoverrides
of the extension.Given the following shared configuration
biome.shared.json
:and the following configuration:
Previously, the
overrides
frombiome.shared.json
was overwritten.It is now merged and results in the following configuration:
Contributed by @Conaclos
Editors
Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where
biome.jsonc
was incorrectly parsed with incorrect options. Contributed by @ematipicoFormatter
The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json
:Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.
This change aligns on Prettier 3.3.3.
This adds clarity to operator precedence.
Contributed by @Conaclos
Keep the parentheses around
infer ... extends
declarations in type unions and type intersections (#3419). Contributed by @ConaclosKeep parentheses around a
yield
expression inside a type assertion.Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
For example, in the following code, Biome now preserves the parentheses.
Contributed by @Conaclos
Remove parentheses around expressions that don't need them inside a decorator.
Biome now matches Prettier in the following cases:
Contributed by @Conaclos
Keep parentheses around objects preceded with a
@satisfies
comment.In the following example, parentheses are no longer removed.
Contributed by @Conaclos
Linter
Promoted rules
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
The following CSS rules are promoted:
The following JavaScript rules are promoted:
Deprecated rules
correctness/noInvalidNewBuiltin
is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.style/useSingleCaseStatement
is deprecated. Use correctness/noSwitchDeclarations instead.suspicious/noConsoleLog
is deprecated. Use suspicious/noConsole instead.New features
Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius
Enhancements
Rename
nursery/noUnknownSelectorPseudoElement
tonursery/noUnknownPseudoElement
. Contributed by @togami2864The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json
:Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos
noBlankTarget now supports an array of allowed domains.
The following configuration allows
example.com
andexample.org
as blank targets.Contributed by @Jayllyz
noConsole now accepts an option that specifies some allowed calls on
console
. Contributed by @ConaclosAdd an
ignoreNull
option for [noDoubleEquals](https://biomejs.dev/linter/rules/no-dConfiguration
📅 Schedule: Branch creation - "every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.