chore(deps): bump the dependencies group with 2 updates

[dependabot]

Bumps the dependencies group with 2 updates: creasi/laravel-nusa and sentry/sentry-laravel.

Updates creasi/laravel-nusa from 0.1.6 to 0.1.7

Release notes

Sourced from creasi/laravel-nusa's releases.

v0.1.7

Features

• ci: init tests on laravel 11 (975fe02)

---

Compare with previous version: creasico/laravel-nusa@v0.1.6...v0.1.7

What's Changed

Contributions

• feat: Initial support for Laravel 11 by @​feryardiant in creasico/laravel-nusa#69

Full Changelog: creasico/laravel-nusa@v0.1.6...v0.1.7

Changelog

Sourced from creasi/laravel-nusa's changelog.

0.1.7 (2024-03-13)

Features

• ci: init tests on laravel 11 (975fe02)

Commits

• 4332031 chore(release): 0.1.7
• 26e2cc0 Merge pull request #69 from creasico/feat/laravel-11
• 5bf6617 chore(ci): drop tests on laravel 9.x
• 975fe02 feat(ci): init tests on laravel 11
• 910b7fd chore(db): update database
• 0c6c849 refactor(static): move static generated csv and json files
• 1a53c74 chore(db): prevent error when importing invalid data from upstream module
• fb64b3a Merge pull request #65 from creasico/dependabot/composer/dependencies-cc98769813
• 2aa3a39 Merge pull request #66 from creasico/dependabot/composer/dev-dependencies-30f...
• dffdd0d Merge pull request #67 from creasico/dependabot/npm_and_yarn/dependencies-4c7...
• Additional commits viewable in compare view

Updates sentry/sentry-laravel from 4.2.0 to 4.4.0

Release notes

Sourced from sentry/sentry-laravel's releases.

4.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.4.0.

Features

• Add support for Laravel 11 Context [(#869)](getsentry/sentry-laravel#869)

  If you are using Laravel 11 and the new "Context" capabilities we now automatically capture that context for you and it will be visible in Sentry. Read more about the feature in the Laravel documentation and how to use it.

4.3.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.1.

Bug Fixes

• Add missing methods to FilesystemDecorator [(#865)](getsentry/sentry-laravel#865)

4.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.0.

Features

• Add support for Laravel 11.0 [(#845)](getsentry/sentry-laravel#845)

  If you're upgrading an existing Laravel 10 application to the new Laravel 11 directory structure, you must change how Sentry integrates into the exception handler. Update your bootstrap/app.php with:

  <?php
  use Illuminate\Foundation\Application;
  use Illuminate\Foundation\Configuration\Exceptions;
  use Illuminate\Foundation\Configuration\Middleware;
  use Sentry\Laravel\Integration;
  return Application::configure(basePath: dirname(DIR))
  ->withRouting(
  web: DIR.'/../routes/web.php',
  commands: DIR.'/../routes/console.php',
  health: '/up',
  )
  ->withMiddleware(function (Middleware $middleware) {
  //
  })
  ->withExceptions(function (Exceptions $exceptions) {
  Integration::handles($exceptions);
  })->create();

  If you plan to perform up-time checks against the new Laravel 11 /up health URL, ignore this transaction in your config/sentry.php file, as not doing so could consume a substantial amount of your performance unit quota.

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

4.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.4.0.

Features

• Add support for Laravel 11 Context [(#869)](getsentry/sentry-laravel#869)

  If you are using Laravel 11 and the new "Context" capabilities we now automatically capture that context for you and it will be visible in Sentry. Read more about the feature in the Laravel documentation and how to use it.

4.3.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.1.

Bug Fixes

• Add missing methods to FilesystemDecorator [(#865)](getsentry/sentry-laravel#865)

4.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.0.

Features

• Add support for Laravel 11.0 [(#845)](getsentry/sentry-laravel#845)

  If you're upgrading an existing Laravel 10 application to the new Laravel 11 directory structure, you must change how Sentry integrates into the exception handler. Update your bootstrap/app.php with:

  <?php
  use Illuminate\Foundation\Application;
  use Illuminate\Foundation\Configuration\Exceptions;
  use Illuminate\Foundation\Configuration\Middleware;
  use Sentry\Laravel\Integration;
  return Application::configure(basePath: dirname(DIR))
  ->withRouting(
  web: DIR.'/../routes/web.php',
  commands: DIR.'/../routes/console.php',
  health: '/up',
  )
  ->withMiddleware(function (Middleware $middleware) {
  //
  })
  ->withExceptions(function (Exceptions $exceptions) {
  Integration::handles($exceptions);
  })->create();

... (truncated)

Commits

• f375fed release: 4.4.0
• 5a79393 Prepare 4.4.0 (#870)
• 6d56923 Add current Laravel context to event (#869)
• 2e77090 Remove "minimum-stability": "dev" (#867)
• 67138e0 Merge branch 'release/4.3.1'
• 631a5eb release: 4.3.1
• f1cb005 Prepare 4.3.1 (#866)
• 6155ed5 Fix docs link (#864)
• 186596e Add missing functions to FilesystemDecorator (#865)
• 6d42ea7 Merge branch 'release/4.3.0'
• Additional commits viewable 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions