chore(deps): update dependency orchestra/testbench to v9.9.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
orchestra/testbench (source)	9.1.2 -> 9.9.0

---

Release Notes

orchestral/testbench (orchestra/testbench)

v9.9.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.9.0+. (v9.8.0...v9.9.0)

Testbench Changes

Added

• Add ability to symlink directory in from skeleton to package.

Changes

• Update skeleton to match v11.5.0.
• Add Orchestra\Testbench\Workbench\Workbench::flushCachedClassAndNamespaces() to flush cached namespaces and classes during installation.
• Use realpath() on vendor:publish output.

v9.8.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.8.0+. (v9.7.0...v9.8.0)

Testbench Changes

Added

• Added Orchestra\Testbench\transform_realpath_to_relative() function.
• Override Laravel's vendor:publish command.

Changes

• Add $force parameter to Orchestra\Testbench\Workbench\Workbench::detectNamespace() method.

v9.7.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.7.0+. (v9.6.2...v9.7.0)

Testbench Changes

Added

• Added ability to detect Workbench namespace via Orchestra\Testbench\Workbench\Workbench::detectNamespace() method.
• Added ability to detect the default user model via Orchestra\Testbench\Workbench\Workbench::applicationUserModel() method.
• Added support for authentication routes within Workbench by configurating workbench.auth config to true.
• Added new package:sync-skeleton command.

Changes

• Testbench Dusk integration improvements:
  • Refactor Orchestra\Testbench\Bootstrap\LoadConfiguration and Orchestra\Testbench\Bootstrap\LoadConfigurationWithWorkbench to allow being extended by Testbench Dusk.
  • Refactor Orchestra\Testbench\Console\Commander.
• Add $tty parameter to Orchestra\Testbench\remote() function.
• Refactor Orchestra\Testbench\Foundation\Bootstrap\CreateVendorSymlink class and mark it as @api.
• Add $backupExistingFile and $resetOnTerminating parameter to following methods in Orchestra\Testbench\Foundation\Console\Concerns\CopyTestbenchFiles trait:
  • copyTestbenchConfigurationFile()
  • copyTestbenchDotEnvFile()
• Supports laravel/serializable-closure v2.

Deprecated

• Deprecate Orchestra\Testbench\Foundation\Console\Concerns\HandleTerminatingConsole trait, use Orchestra\Testbench\Foundation\Console\TerminatingConsole class instead.

v9.6.1

Compare Source

Changes

• Update minimum support for Testbench Core v9.6.2+. (v9.6.0...v9.6.2)

Testbench Changes

Fixes

• Fixes route:cache when health: true configured using testbench.yaml.
• Fixes compatibility with Laravel Framework v11.33.0.

v9.6.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.6.0+. (v9.5.3...v9.6.0)

Testbench Changes

Added

• Added Orchestra\Testbench\Foundation\Bootstrap\DeleteVendorSymlink class.
• Added Orchestra\Testbench\Concerns\InteractsWithMockery trait.
• Added --database option to package:create-sqlite-db command.
• Added --database and --all options to package:drop-sqlite-db command.
• Added Orchestra\Testbench\php_binary() function.
• Allows laravel/serializable-closure 2.
• Added draft support for PHP 8.4.

Changes

• Ensure database directory exists when running package:create-sqlite-db.
• Allow configuring PHP_CLI_SERVER_WORKERS via Composer Script.
• Improves CTRL+C and CTRL+BREAK supports on Windows without pcntl extension.
• Orchestra\Testbench\Foundation\Console\Actions\GeneratesFile should be able to handle $from and $to when given as false or null.

Fixed

• Fixed #[WithMigration('queue')] should load the default migrations.

v9.5.2

Compare Source

Changes

• Update minimum support for Testbench Core v9.5.3+. (v9.5.2...v9.5.3)

Testbench Changes

Fixes

• Prevent seeder from being executed when shouldSeed() exists and return false.

v9.5.1

Compare Source

Changes

• Update minimum support for Testbench Core v9.5.2+. (v9.5.0...v9.5.2)

Testbench Changes

Changes

• Listen to SIGHUP, SIGUSR1, and SIGUSR2 signals via Testbench CLI.
• Update config/concurrency.php configuration file.

Fixes

• Fixes Testbench CLI signals via serve command to reset published .env and testbench.yaml.

v9.5.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.5.0+. (v9.4.0...v9.5.0)

Testbench Changes

Added

• Added Orchestra\Testbench\Attributes\RequiresDatabase attribute class.
• Added markTestSkippedWhen() and markTestSkippedUnless() assertion helper to conditionally handle markTestSkipped().
• Added Orchestra\Testbench\default_migration_path() helper function.
• Added Orchestra\Testbench\laravel_vendor_exists() helper function.
• Allows TestCase to inherit Attributes defined on parent TestCase by @​BlackLanzer in #​233.

Changes

• Allow Testbench to delete vendor symlink directory if it was created while running tests.

Fixes

• Fixes view.paths configuration not being updated to include workbench/resources/views due to IoC booting sequence.

Deprecated

• Deprecated Orchestra\Testbench\laravel_migration_path(), use default_migration_path() instead.

New Contributors

• @​BlackLanzer made their first contribution in https://github.com/orchestral/testbench-core/pull/233

v9.4.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.4.0+. (v9.3.0...v9.4.0)

Testbench Changes

Added

• Added artisan binary to Laravel skeleton.
• Added Orchestra\Testbench\join_paths() function.
• Added Orchestra\Testbench\Attributes\UsesVendor attribute class.
• Added defineStashRoutes() method to register adhoc route for test.

Changes

• Improvements to Orchestra\Testbench\default_skeleton_path(), Orchestra\Testbench\package_path(), and Orchestra\Testbench\workbench_path() usage based on new Orchestra\Testbench\join_paths() function.

v9.3.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.3.0+. (v9.2.0...v9.3.0)

Testbench Changes

Changes

• Update Orchestra\Testbench\Foundation\Console\Actions\GeneratesFile to remove .gitkeep file when directory contain one or more files.
• Code Improvements.

Fixes

• Fixes InteractsWithPublishedFiles should only flush published files within database/migrations directory.

v9.2.0

Compare Source

Changes

• Update minimum support for Testbench Core v9.2.0+. (v9.1.3...v9.2.0)

Testbench Changes

Added

• Added new attributes:
  • Orchestra\Testbench\Attributes\ResolvesLaravel
  • Orchestra\Testbench\Attributes\UsesFrameworkConfiguration
• Allows to discover factories using Workbench to map Workbench\App\Models to Workbench\Database\Factories classes.
• Allows to auto discover console command classes from workbench/app/Console/Commands.

Changes

• Bump minimum support to Laravel Framework v11.11.
• Implements JsonSerializable to Orchestra\Testbench\Foundation\UndefinedValue.
• Update skeleton to use workbench as default environment value.
• Allow Orchestra\Testbench\Attributes\Define and Orchestra\Testbench\Attributes\DefineEnvironment to be used on the class level by @​danjohnson95

Fixes

• Ensure usesTestingFeature() attribute registration is loaded before class attributes instead of method attributes.

---

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.

---

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>.
  • 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.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.50%. Comparing base (141ffaf) to head (fa0335c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #217      +/-   ##
============================================
+ Coverage     98.43%   98.50%   +0.07%     
  Complexity       74       74              
============================================
  Files            15       15              
  Lines           255      268      +13     
============================================
+ Hits            251      264      +13     
  Misses            4        4              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: composer update orchestra/testbench:9.9.0 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Dependency laravel/framework is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency phpunit/phpunit is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/yaml is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/console) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/contracts) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/log) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/process) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/support) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/database) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/filesystem) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency laravel/framework (via replace of illuminate/queue) is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency rector/rector is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency ramsey/uuid is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires orchestra/testbench ^9.1 -> satisfiable by orchestra/testbench[v9.9.0].
    - orchestra/testbench v9.9.0 requires laravel/framework ^11.35.0 -> found laravel/framework[v11.35.0, v11.35.1, v11.36.0, v11.36.1] but the package is fixed to v11.13.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.