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.

Sign up for GitHub

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

Jump to bottom

⬆️ chore(deps): Update all non-major dependencies #82

Merged
merged 3 commits into from
May 3, 2024
Merged

⬆️ chore(deps): Update all non-major dependencies #82

merged 3 commits into from
May 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 9, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@biomejs/biome (source) 1.5.3 -> 1.7.2 age adoption passing confidence
@vitest/coverage-istanbul (source) 1.3.1 -> 1.5.3 age adoption passing confidence
gitmoji-cli 9.1.0 -> 9.2.0 age adoption passing confidence
markdownlint-cli2 0.12.1 -> 0.13.0 age adoption passing confidence
turbo (source) 1.12.5 -> 1.13.3 age adoption passing confidence
type-fest 4.11.1 -> 4.18.0 age adoption passing confidence
typescript (source) 5.4.2 -> 5.4.5 age adoption passing confidence
vite-tsconfig-paths 4.3.1 -> 4.3.2 age adoption passing confidence
vitepress (source) 1.0.0-rc.45 -> 1.1.4 age adoption passing confidence
vitest (source) 1.3.1 -> 1.5.3 age adoption passing confidence
zod (source) 3.22.4 -> 3.23.5 age adoption passing confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v1.7.2

Compare Source

Analyzer
Bug fixes

  • Import sorting now ignores side effect imports (#​817).

    A side effect import consists now in its own group.
    This ensures that side effect imports are not reordered.

    Here is an example of how imports are now sorted:

      import "z"
- import { D } from "d";
  import { C } from "c";
+ import { D } from "d";
  import "y"
  import "x"
- import { B } from "b";
  import { A } from "a";
+ import { B } from "b";
  import "w"

    Contributed by @​Conaclos

  • Import sorting now adds spaces where needed (#​1665)
    Contributed by @​Conaclos

CLI
Bug fixes

  • biome migrate eslint now handles cyclic references.

    Some plugins and configurations export objects with cyclic references.
    This causes biome migrate eslint to fail or ignore them.
    These edge cases are now handled correctly.

    Contributed by @​Conaclos

Formatter
Bug fixes
  • Correctly handle placement of comments inside named import clauses. #​2566. Contributed by @​ah-yu
Linter
New features
Bug fixes

  • noDuplicateJsonKeys no longer crashes when a JSON file contains an unterminated string (#​2357).
    Contributed by @​Conaclos

  • noRedeclare now reports redeclarations of parameters in a functions body (#​2394).

    The rule was unable to detect redeclarations of a parameter or type parameter in the function body.
    The following two redeclarations are now reported:

    function f<T>(a) {
  type T = number; // redeclaration
  const a = 0; // redeclaration
}

    Contributed by @​Conaclos

  • noRedeclare no longer reports overloads in object types (#​2608).

    The rule no longer report redeclarations in the following code:

    type Overloads = {
  ({ a }: { a: number }): number,
  ({ a }: { a: string }): string,
};

    Contributed by @​Conaclos

  • noRedeclare now merge default function export declarations and types (#​2372).

    The following code is no longer reported as a redeclaration:

    interface Foo {}
export default function Foo() {}

    Contributed by @​Conaclos

  • noUndeclaredVariables no longer reports variable-only and type-only exports (#​2637).
    Contributed by @​Conaclos

  • [noUnusedVariables] no longer crash Biome when encountering a malformed conditional type (#​1695).
    Contributed by @​Conaclos

  • useConst now ignores a variable that is read before its assignment.

    Previously, the rule reported the following example:

    let x;
x; // read
x = 0; // write

    It is now correctly ignored.

    Contributed by @​Conaclos

  • useShorthandFunctionType now suggests correct code fixes when parentheses are required (#​2595).

    Previously, the rule didn't add parentheses when they were needed.
    It now adds parentheses when the function signature is inside an array, a union, or an intersection.

    - type Union = { (): number } | string;
+ type Union = (() => number) | string;

    Contributed by @​Conaclos

  • useTemplate now correctly escapes strings (#​2580).

    Previously, the rule didn't correctly escape characters preceded by an escaped character.

    Contributed by @​Conaclos

  • noMisplacedAssertion now allow these matchers

    • expect.any()
    • expect.anything()
    • expect.closeTo
    • expect.arrayContaining
    • expect.objectContaining
    • expect.stringContaining
    • expect.stringMatching
    • expect.extend
    • expect.addEqualityTesters
    • expect.addSnapshotSerializer

    Contributed by @​fujiyamaorange

Parser
Bug fixes

  • The language parsers no longer panic on unterminated strings followed by a newline and a space (#​2606, #​2410).

    The following example is now parsed without making Biome panics:

    "
 "

    Contributed by @​Conaclos

v1.7.1

Compare Source

Editors
Bug fixes
Formatter
Bug fixes

  • Add parentheses for the return expression that has leading multiline comments. #​2504. Contributed by @​ah-yu

  • Correctly format dangling comments of continue statements. #​2555. Contributed by @​ah-yu

Linter
Bug fixes
  • Fix case where jsxRuntime wasn't being respected by useImportType rule (#​2473).Contributed by @​arendjr
  • Fix #​2460, where the rule noUselessFragments was crashing the linter in some cases. Now cases like these are correctly handled: 
    callFunction(<>{bar}</>)
    Contributed by @​ematipico
  • Fix #​2366, where noDuplicateJsonKeys incorrectly computed the kes to highlight. Contributed by @​ematipico
Enhancements
  • The rule noMisplacedAssertions now considers valid calling expect inside waitFor: 
    import { waitFor } from '@&#8203;testing-library/react';

await waitFor(() => {
  expect(111).toBe(222);
});
    Contributed by @​ematipico

v1.7.0

Compare Source

Analyzer
Bug fixes

  • Now Biome can detect the script language in Svelte and Vue script blocks more reliably (#​2245). Contributed by @​Sec-ant

  • useExhaustiveDependencies no longer reports recursive calls as missing
    dependencies (#​2361).
    Contributed by @​arendjr

  • useExhaustiveDependencies correctly reports missing dependencies declared
    using function declarations (#​2362).
    Contributed by @​arendjr

  • Biome now can handle .svelte and .vue files with CRLF as the end-of-line sequence. Contributed by @​Sec-ant

  • noMisplacedAssertion no longer reports method calls by describe, test, it objects (e.g. test.each([])()) (#​2443). Contributed by @​unvalley.

  • Biome now can handle .vue files with generic components (#​2456).

    <script generic="T extends Record<string, any>" lang="ts" setup>
//...
</script>

    Contributed by @​Sec-ant

Enhancements

  • Complete the well-known file lists for JSON-like files. Trailing commas are allowed in .jsonc files by default. Some well-known files like tsconfig.json and .babelrc don't use the .jsonc extension but still allow comments and trailing commas. While others, such as .eslintrc.json, only allow comments. Biome is able to identify these files and adjusts the json.parser.allowTrailingCommas option accordingly to ensure they are correctly parsed. Contributed by @​Sec-ant

  • Fix dedent logic inconsistent with prettier where the indent-style is space and the indent-width is not 2. Contributed by @​mdm317

CLI
New features

  • Add a command to migrate from ESLint

    biome migrate eslint allows you to migrate an ESLint configuration to Biome.
    The command supports legacy ESLint configurations and new flat ESLint configurations.
    Legacy ESLint configurations using the YAML format are not supported.

    When loading a legacy ESLint configuration, Biome resolves the extends field.
    It resolves both shared configurations and plugin presets!
    To do this, it invokes Node.js.

    Biome relies on the metadata of its rules to determine the equivalent rule of an ESLint rule.
    A Biome rule is either inspired or roughly identical to an ESLint rules.
    By default, inspired and nursery rules are excluded from the migration.
    You can use the CLI flags --include-inspired and --include-nursery to migrate them as well.

    Note that this is a best-effort approach.
    You are not guaranteed to get the same behavior as ESLint.

    Given the following ESLint configuration:

    {
      "ignore_patterns": ["**/*.test.js"],
      "globals": { "var2": "readonly" },
      "rules": {
          "eqeqeq": "error"
      },
      "overrides": [{
          "files": ["lib/*.js"],
          "rules": {
            "default-param-last": "off"
          }
      }]
}

    biome migrate eslint --write changes the Biome configuration as follows:

    {
  "linter": {
    "rules": {
      "recommended": false,
      "suspicious": {
        "noDoubleEquals": "error"
      }
    }
  },
  "javascript": { "globals": ["var2"] },
  "overrides": [{
    "include": ["lib/*.js"],
    "linter": {
      "rules": {
        "style": {
          "useDefaultParameterLast": "off"
        }
      }
    }
  }]
}

    Also, if the working directory contains .eslintignore, then Biome migrates the glob patterns.
    Nested .eslintignore in subdirectories and negated glob patterns are not supported.

    If you find any issue, please don't hesitate to report them.

    Contributed by @​Conaclos

  • Added two new options to customise the emitted output of the CLI: --reporter=json and --reporter=json-pretty. With --reporter=json, the diagnostics and the
    summary will be printed in the terminal in JSON format. With --reporter=json-pretty, you can print the same information, but formatted using the same options of your configuration.

    NOTE: the shape of the JSON is considered experimental, and the shape of the JSON might change in the future.

    Example of output when running `biome format` command ```json { "summary": { "changed": 0, "unchanged": 1, "errors": 1, "warnings": 0, "skipped": 0, "suggestedFixesSkipped": 0, "diagnosticsNotPrinted": 0 }, "diagnostics": [ { "category": "format", "severity": "error", "description": "Formatter would have printed the following content:", "message": [ { "elements": [], "content": "Formatter would have printed the following content:" } ], "advices": { "advices": [ { "diff": { "dictionary": " statement();\n", "ops": [ { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [2, 12] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [12, 13] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "insert": { "range": [13, 15] } } } ] } } ] }, "verboseAdvices": { "advices": [] }, "location": { "path": { "file": "format.js" }, "span": null, "sourceCode": null }, "tags": [], "source": null } ], "command": "format" } ```

  • Added new --staged flag to the check, format and lint subcommands.

    This new option allows users to apply the command only to the files that are staged (the
    ones that will be committed), which can be very useful to simplify writing git hook scripts
    such as pre-commit. Contributed by @​castarco

Enhancements

  • Improve support of .prettierignore when migrating from Prettier

    Now, Biome translates most of the glob patterns in .prettierignore to the equivalent Biome ignore pattern.
    Only negated glob patterns are not supported.

    Contributed by @​Conaclos

  • Support JavaScript configuration files when migrating from Prettier

    biome migrate prettier is now able to migrate Prettier configuration files
    ending with js, mjs, or cjs extensions.
    To do this, Biome invokes Node.js.

    Also, embedded Prettier configurations in package.json are now supported.

    Contributed by @​Conaclos

  • Support overrides field in Prettier configuration files when migrating from Prettier.
    Contributed by @​Conaclos

  • Support passing a file path to the --config-path flag or the BIOME_CONFIG_PATH environment variable.

    Now you can pass a .json/.jsonc file path with any filename to the --config-path flag or the
    BIOME_CONFIG_PATH environment variable. This will disable the configuration auto-resolution and Biome
    will try to read the configuration from the said file path (#​2265).

    biome format --config-path=../biome.json ./src

    Contributed by @​Sec-ant

Bug fixes

  • Biome now tags the diagnostics emitted by organizeImports and formatter with correct severity levels, so they will be properly filtered by the flag --diagnostic-level (#​2288). Contributed by @​Sec-ant

  • Biome now correctly filters out files that are not present in the current directory when using the --changed flag #​1996. Contributed by @​castarco

  • Biome now skips traversing fifo or socket files (#​2311). Contributed by @​Sec-ant

  • Biome now resolves configuration files exported from external libraries in extends from the working directory (CLI) or project root (LSP). This is the documented behavior and previous resolution behavior is considered as a bug (#​2231). Contributed by @​Sec-ant

Configuration
Bug fixes

  • Now setting group level all to false can disable recommended rules from that group when top level recommended is true or unset. Contributed by @​Sec-ant

  • Biome configuration files can correctly extends .jsonc configuration files now (#​2279). Contributed by @​Sec-ant

  • Fixed the JSON schema for React hooks configuration (#​2396). Contributed by @​arendjr

Enhancements

  • Biome now displays the location of a parsing error for its configuration file (#​1627).

    Previously, when Biome encountered a parsing error in its configuration file,
    it didn't indicate the location of the error.
    It now displays the name of the configuration file and the range where the error occurred.

    Contributed by @​Conaclos

  • options is no longer required for rules without any options (#​2313).

    Previously, the JSON schema required to set options to null when an object is used to set the diagnostic level of a rule without any option.
    However, if options is set to null, Biome emits an error.

    The schema is now fixed and it no longer requires specifying options.
    This makes the following configuration valid:

    {
  "linter": {
    "rules": {
      "style": {
        "noDefaultExport": {
          "level": "off"
        }
      }
    }
  }
}

    Contributed by @​Conaclos

Editors
Bug fixes
Formatter
Bug fixes
  • Fix #​2291 by correctly handle comment placement for JSX spread attributes and JSX spread children. Contributed by @​ah-yu
JavaScript APIs
Linter
Promoted rules

New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
The following rules are promoted:

New features
Enhancements

  • style/useFilenamingConvention now allows prefixing a filename with + (#​2341).

    This is a convention used by Sveltekit and Vike.

    Contributed by @​Conaclos

  • style/useNamingConvention now accepts PascalCase for local and top-level variables.

    This allows supporting local variables that hold a component or a regular class.
    The following code is now accepted:

    function loadComponent() {
  const Component = getComponent();
  return <Component />;
}

    Contributed by @​Conaclos

  • complexity/useLiteralKeys no longer report computed properties named __proto__ (#​2430).

    In JavaScript, {["__proto__"]: null} and {__proto__: null} have not the same semantic.
    The first code set a regular property to null.
    The second one set the prototype of the object to null.
    See the MDN Docs for more details.

    The rule now ignores computed properties named __proto__.

    Contributed by @​Conaclos

Bug fixes

  • Lint rules useNodejsImportProtocol, useNodeAssertStrict, noRestrictedImports, noNodejsModules will no longer check declare module statements anymore. Contributed by @​Sec-ant

  • style/useNamingConvention now accepts any case for variables from object destructuring (#​2332).

    The following name is now ignored:

    const { Strange_Style } = obj;

    Previously, the rule renamed this variable. This led to a runtime error.

    Contributed by @​Conaclos

Parser
Bug fixes
  • Fixed an issue when Unicode surrogate pairs were encoded in JavaScript strings
    using an escape sequence (#​2384).
    Contributed by @​arendjr

v1.6.4

Compare Source

Analyzer
Bug fixes
  • An operator with no spaces around in a binary expression no longer breaks the js analyzer (#​2243). Contributed by @​Sec-ant
CLI
Bug fixes
Configuration
Bug fixes
  • Correctly calculate enabled rules in lint rule groups. Now a specific rule belonging to a group can be enabled even if its group-level preset option recommended or all is false (#​2191). Contributed by @​Sec-ant
Editors
Bug fixes
  • Fix the unexpected code deletion and repetition when quickfix.biome is enabled and some import-related rules are applied (#​2222, #​688, #​1015). Contributed by @​Sec-ant
Linter
Bug fixes

  • Fix #​2211. noChildrenProp should work fine when children pass as a prop in a new line. Contributed by @​fireairforce

  • Fix #​2248. lint/a11y/useButtonType should not trigger when button element with spread attribute. Contributed by @​fireairforce

  • Fix #​2216. lint/style/useNamingConvention should not ignore JSX Component name binding. Contributed by @​fireairforce

Enhancements
  • Add support for object property members in the rule useSortedClasses. Contributed by @​ematipico
Parser
  • The parser doesn't throw any error when the frontmatter of .astro files contains an illegal return:

v1.6.3

Compare Source

Analyzer
CLI
Bug fixes

  • Fix configuration resolution. Biome is now able to correctly find the biome.jsonc configuration file when --config-path is explicitly set (#​2164). Contributed by @​Sec-ant

  • JavaScript/TypeScript files of different variants (.ts, .js, .tsx, .jsx) in a single workspace now have stable formatting behaviors when running the CLI command in paths of different nested levels or in different operating systems (#​2080, #​2109). Contributed by @​Sec-ant

Configuration
Bug fixes
  • Complete the documentation and overrides support for options formatter.lineEnding, [language].formatter.lineEnding, formatter.attributePosition and javascript.formatter.attributePosition. Contributed by @​Sec-ant
Editors
Formatter
Bug fixes
  • Fix #​2172 by breaking long object destructuring patterns. Contributed by @​ah-yu
JavaScript APIs
Linter
New features
Enhancements
  • Rename noSemicolonInJsx to noSuspiciousSemicolonInJsx. Contributed by @​fujiyamaorange
LSP
Bug fixes
  • Quickfix action no longer autofixes lint rule errors on save when linter is disabled (#​2161). Contributed by @​Sec-ant
  • Range formatting for Astro/Svelte/Vue doesn't place code out of place, especially when formatting on paste is enabled. Contributed by @​ematipico
Parser

v1.6.2

Compare Source

Analyzer
Bug fixes

  • The noSuperWithoutExtends rule now allows for calling super() in derived class constructors of class expressions (#​2108). Contributed by @​Sec-ant

  • Fix discrepancies on file source detection. Allow module syntax in .cts files (#​2114). Contributed by @​Sec-ant

CLI
Bug fixes

  • Fixes #​2131, where folders were incorrectly ignored when running the command check. Now folders are correctly ignored based on their command. Contributed by @​ematipico

  • Smoother handling of "endOfLine": "auto" in prettier migration: falling back to "lf" (#​2145). Contributed by @​eMerzh

Configuration
Bug fixes
  • Fix enabled rules calculation. The precendence of individual rules, all and recommend presets in top-level and group-level configs is now correctly respected. More details can be seen in (#​2072) (#​2028). Contributed by @​Sec-ant
Formatter
Bug fixes
  • Fix #​1661. Now nested conditionals are aligned with Prettier's logic, and won't contain mixed spaces and tabs. Contributed by @​ematipico
JavaScript APIs
Enhancements
  • Support applying lint fixes when calling the lintContent method of the Biome class (#​1956). Contributed by @​mnahkies
Linter
Bug fixes

  • Rule noUndeclaredDependencies now also validates peerDependencies and optionalDependencies (#​2122). Contributed by @​Sec-ant

  • Rule noUndeclaredDependencies won't check declare module statements anymore (#​2123). Contributed by @​Sec-ant

  • Fix #​1925. The fix for useOptionalChain would sometimes suggest an incorrect fix that discarded optional chaining operators on the left-hand side of logical expressions. These are now preserved. Contributed by @​arendjr

  • Rule noUndeclaredVariables now also checks for worker globals (#​2121). Contributed by @​Sec-ant

LSP
Bug fixes

  • Correctly parse .jsonc files. Contributed by @​Sec-ant

  • Correctly resolve external extends configs. Contributed by @​Sec-ant

v1.6.1

Compare Source

CLI
Bug fixes
  • CLI is now able to automatically search and resolve biome.jsonc (#​2008). Contributed by @​Sec-ant
  • Fix a false positive where some files were counted as "fixed" even though they weren't modified. Contributed by @​ematipico
Configuration
Bug fixes
  • json.formatter.trailingCommas option now works in overrides (#​2009). Contributed by @​Sec-ant
Linter
New features

  • Add rule noDoneCallback, this rule checks the function parameter of hooks & tests
    for use of the done argument, suggesting you return a promise instead. Contributed by @​vasucp1207

    beforeEach(done => {
  // ...
});
Bug fixes
Parser
Bug fixes

  • JavaScript lexer is now able to lex regular expression literals with escaped non-ascii chars (#​1941).

    Contributed by @​Sec-ant

v1.6.0

Compare Source

Analyzer
New features
  • Add partial for .astro files. Biome is able to sort imports inside the frontmatter of the Astro files. Contributed
    by @​ematipico
vitest-dev/vitest (@​vitest/coverage-istanbul)

v1.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - "before 4am" (UTC).

🚦 Automerge: Enabled.

♻ 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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel Vercel
Copy link

vercel bot commented Mar 9, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
repository-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 3, 2024 11:50am

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Mar 9, 2024 •
edited
Loading

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 30, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@github-actions GitHub Actions
Copy link

github-actions bot commented May 3, 2024

Coverage Report for packages/repository

Status Category Percentage Covered / Total
🟢 Lines 96.83% (🎯 80%) 153 / 158
🟢 Statements 97.02% (🎯 80%) 163 / 168
🟢 Functions 95.71% (🎯 80%) 67 / 70
🟢 Branches 92.47% (🎯 80%) 86 / 93
File CoverageNo changed files found.
Generated in workflow #156

@grixu grixu merged commit 442d6f6 into main May 3, 2024
4 checks passed
@grixu grixu deleted the deps/all-minor-patch branch May 3, 2024 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@grixu grixu grixu approved these changes

@grzywaczek grzywaczek Awaiting requested review from grzywaczek grzywaczek is a code owner

@Mat3uszkek Mat3uszkek Awaiting requested review from Mat3uszkek

@matdudek matdudek Awaiting requested review from matdudek

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@grixu