build(deps-dev): bump @effect/language-service from 0.57.1 to 0.58.2

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps @effect/language-service from 0.57.1 to 0.58.2.

Release notes

Sourced from @​effect/language-service's releases.

v0.58.2

Patch Changes

• #510 9064174 Thanks @​mattiamanzati! - Extend anyUnknownInErrorContext diagnostic to also check Layer types

  The anyUnknownInErrorContext diagnostic now checks both Effect and Layer types for any or unknown in their error and requirements channels. This helps catch more cases where type information is being lost in your Effect applications.

  Example:

  const effectUnknown = Effect.context<unknown>();
  const layerUnknown = Layer.effectDiscard(effectUnknown);
  // Now reports: This has unknown in the requirements channel which is not recommended.

  The diagnostic also now skips explicit Layer type annotations to avoid false positives on intentional type declarations.

v0.58.1

Patch Changes

• #508 1a4446c Thanks @​mattiamanzati! - Fix anyUnknownInErrorContext diagnostic to exclude JSX elements from reporting false positives. The diagnostic will no longer incorrectly flag JSX tag names, self-closing elements, opening/closing elements, and attribute names.

  Example:

  // Before: Would incorrectly report diagnostic on <MyComponent />
  const element = <MyComponent />;
  // After: No diagnostic, JSX elements are properly excluded
  const element = <MyComponent />;

v0.58.0

Minor Changes

• #505 31cff49 Thanks @​clayroach! - Enhance diagnostics CLI command with new options for CI/CD integration and tooling:

  • --format: Output format selection (json, pretty, text, github-actions)

    • json: Machine-readable JSON output with structured diagnostics and summary
    • pretty: Colored output with context (default, original behavior)
    • text: Plain text output without colors
    • github-actions: GitHub Actions workflow commands for inline PR annotations

  • --strict: Treat warnings as errors (affects exit code)

  • --severity: Filter diagnostics by severity level (comma-separated: error, warning, message)

  • Exit codes: Returns exit code 1 when errors are found (or warnings in strict mode)

... (truncated)

Changelog

Sourced from @​effect/language-service's changelog.

0.58.2

Patch Changes

• #510 9064174 Thanks @​mattiamanzati! - Extend anyUnknownInErrorContext diagnostic to also check Layer types

  The anyUnknownInErrorContext diagnostic now checks both Effect and Layer types for any or unknown in their error and requirements channels. This helps catch more cases where type information is being lost in your Effect applications.

  Example:

  const effectUnknown = Effect.context<unknown>();
  const layerUnknown = Layer.effectDiscard(effectUnknown);
  // Now reports: This has unknown in the requirements channel which is not recommended.

  The diagnostic also now skips explicit Layer type annotations to avoid false positives on intentional type declarations.

0.58.1

Patch Changes

• #508 1a4446c Thanks @​mattiamanzati! - Fix anyUnknownInErrorContext diagnostic to exclude JSX elements from reporting false positives. The diagnostic will no longer incorrectly flag JSX tag names, self-closing elements, opening/closing elements, and attribute names.

  Example:

  // Before: Would incorrectly report diagnostic on <MyComponent />
  const element = <MyComponent />;
  // After: No diagnostic, JSX elements are properly excluded
  const element = <MyComponent />;

0.58.0

Minor Changes

• #505 31cff49 Thanks @​clayroach! - Enhance diagnostics CLI command with new options for CI/CD integration and tooling:

  • --format: Output format selection (json, pretty, text, github-actions)

    • json: Machine-readable JSON output with structured diagnostics and summary
    • pretty: Colored output with context (default, original behavior)
    • text: Plain text output without colors
    • github-actions: GitHub Actions workflow commands for inline PR annotations

  • --strict: Treat warnings as errors (affects exit code)

  • --severity: Filter diagnostics by severity level (comma-separated: error, warning, message)

... (truncated)

Commits

• 9f4117e Version Packages (#511)
• 9064174 Extend anyUnknownInErrorContext diagnostic to Layer types (#510)
• cd4b03c Version Packages (#509)
• 1a4446c Fix anyUnknownInErrorContext diagnostic for JSX elements (#508)
• bac505c Version Packages (#506)
• 48c7d9a Cleanup diagnostics formatting (#507)
• 31cff49 feat: cli diagnostics enhancements (#505)
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)