chore(deps): update dependency pointfreeco/swift-dependencies to from: "1.9.2"

[renovate]

This PR contains the following updates:

Package	Update	Change
pointfreeco/swift-dependencies	minor	from: "1.7.0" -> from: "1.9.2"

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

pointfreeco/swift-dependencies (pointfreeco/swift-dependencies)

v1.9.2

Compare Source

What's Changed

• [Fixed] Allow dependencies test trait to throw.https://github.com/pointfreeco/swift-dependencies/pull/3599
• [Infrastructure] Remove no longer relevant warning in Designing dependencies documentation page by @​gsl-sebastienpecoul in https://github.com/pointfreeco/swift-dependencies/pull/357

Full Changelog: pointfreeco/swift-dependencies@1.9.1...1.9.2

v1.9.1

Compare Source

What's Changed

• Fixed: Resolve issue with @DependencyEndpoint not reporting errors when a custom closure is provided (thanks @​gpambrozio, https://github.com/pointfreeco/swift-dependencies/pull/355).

New Contributors

• @​gpambrozio made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/355

Full Changelog: pointfreeco/swift-dependencies@1.9.0...1.9.1

v1.9.0

Compare Source

What's Changed

• Added: shouldReportUnimplemented, for detecting if a test value should report an issue upon access (https://github.com/pointfreeco/swift-dependencies/pull/352).
• Fixed: Use proper access control when @DependencyEndpoint macro generates method with package (thanks @​gsl-sebastienpecoul, https://github.com/pointfreeco/swift-dependencies/pull/350).
• Fixed: Undeprecate preview traits (https://github.com/pointfreeco/swift-dependencies/pull/353). We have discovered a workaround for the bug causing their initial deprecation.

New Contributors

• @​gsl-sebastienpecoul made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/350

Full Changelog: pointfreeco/swift-dependencies@1.8.1...1.9.0

v1.8.1

Compare Source

What's Changed

• Fixed: Strip trailing comments from endpoints. https://github.com/pointfreeco/swift-dependencies/pull/347
• Infrastructure: responsibly -> responsible in Testing article by @​agarrharr. https://github.com/pointfreeco/swift-dependencies/pull/345

New Contributors

• @​agarrharr made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/345

Full Changelog: pointfreeco/swift-dependencies@1.8.0...1.8.1

v1.8.0

Compare Source

What's Changed

• Added: Test trait enhancements (https://github.com/pointfreeco/swift-dependencies/pull/342, https://github.com/pointfreeco/swift-dependencies/pull/344).

  The .dependencies and .dependency test traits now use Swift 6.1's TestScoping when available, leading to more reliable dependency injection.

  The .dependencies trait can also now be used in a "bare" fashion on a base test suite to ensure all tests are given a unique set of dependencies by default:

  @​Suite(.dependencies) struct BaseTests {}

• Fixed: Avoid test data race in dependency cache (https://github.com/pointfreeco/swift-dependencies/pull/303).

• Infrastructure: Update .spi.yml (thanks @​finestructure, https://github.com/pointfreeco/swift-dependencies/pull/336).

• Infrastructure: Add Swift 6.0 to Linux test matrix (thanks @​finestructure, https://github.com/pointfreeco/swift-dependencies/pull/303).

• Infrastructure: Added tests for prepareDependencies and updated docs (https://github.com/pointfreeco/swift-dependencies/pull/337)

Full Changelog: pointfreeco/swift-dependencies@1.7.0...1.8.0

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

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

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.