chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@envelop/core (source)	5.1.1 -> 5.2.0
@envelop/live-query (source)	8.0.1 -> 8.1.0
svelte (source)	5.21.0 -> 5.22.0

---

Release Notes

n1ru4l/envelop (@​envelop/core)

v5.2.0

Compare Source

Minor Changes

• #​2430
  a107c89
  Thanks @​EmrysMyrddin! - ## New Instruments API

  Introducation of a new API allowing to instrument the graphql pipeline.

  This new API differs from already existing Hooks by not having access to intup/output of phases.
  The goal of Instruments is to run allow running code before, after or araound the whole
  process of a phase, incuding plugins hooks executions.

  The main use case of this new API is observability (monitoring, tracing, etc...).

Basic usage

import { envelop } from '@​envelop/core'
import Sentry from '@​sentry/node'

const getEnveloped = envelop({
  plugins: [
    {
      instruments: {
        execute: ({ context }, wrapped) =>
          Sentry.startSpan({ name: 'Graphql Operation' }, async () => {
            try {
              await wrapped()
            } catch (err) {
              Sentry.captureException(err)
            }
          })
      }
    }
  ]
})

Mutliple instruments plugins

It is possilbe to have multiple instruments plugins (Prometheus and Sentry for example), they will
be automatically composed by envelop in the same order than the plugin array (first is outtermost,
last is inner most).

import { useOpentelemetry } from '@​envelop/opentelemetry'
import { useSentry } from '@​envelop/sentry'

const getEnveloped = envelop({
  plugins: [useSentry(), useOpentelemetry()]
})

sequenceDiagram
  Sentry->>Opentelemetry: ;
  Opentelemetry->>Envelop: ;
  Envelop->>Opentelemetry: ;
  Opentelemetry->>Sentry: ;

Loading

Custom instruments ordering

If the default composition ordering doesn't suite your need, you can mannually compose
instruments. This allows to have a different execution order of hooks and instruments.

import { useOpentelemetry } from '@​envelop/opentelemetry'
import { composeInstruments, useSentry } from '@​envelop/sentry'

const { instruments: sentryInstruments, ...sentryPlugin } = useSentry()
const { instruments: otelInstruments, ...otelPlugin } = useOpentelemetry()
const instruments = composeInstruments([otelInstruments, sentryInstruments])

const getEnveloped = envelop({
  plugins: [{ instruments }, sentryPlugin, otelPlugin]
})

sequenceDiagram
  Opentelemetry->>Sentry: ;
  Sentry->>Envelop: ;
  Envelop->>Sentry: ;
  Sentry->>Opentelemetry: ;

Loading

Patch Changes

• #​2430
  a107c89
  Thanks @​EmrysMyrddin! - dependencies updates:
  • Added dependency
    @envelop/instruments@workspace:^ ↗︎
    (to dependencies)
• Updated dependencies
  [a107c89]:
  • @​envelop/types@​5.2.0

n1ru4l/envelop (@​envelop/live-query)

v8.1.0

Compare Source

Patch Changes

• Updated dependencies
  [a107c89,
  a107c89]:
  • @​envelop/core@​5.2.0

sveltejs/svelte (svelte)

v5.22.0

Minor Changes

• feat: Add idPrefix option to render (#​15428)

Patch Changes

• fix: make dialog element and role interactive (#​15429)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f5f4f97

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://b1a10fa0.graphql-tools.pages.dev