Remove unused view loading and bump deps

[gvieira18]

Summary

• Remove unused loadViewsFrom calls from Events and Identity service providers (no views exist in those modules)
• Bump dependencies: laracord/framework pinned to e7b64d6, nightwatch 1.28, debugbar 4.3, boost 2.4.9, sail 1.62

Test plan

• Verify Events module still boots correctly
• Verify Identity module still boots correctly
• Run composer install from clean state

---

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR modifies two module service providers to load package migrations instead of views during boot. EventsServiceProvider and IdentityServiceProvider now call loadMigrationsFrom() to register migrations from their database/migrations directories, replacing the previous view registration. Additionally, composer.json dependency versions are updated: laracord/framework is pinned to a specific commit, laravel/nightwatch is bumped to ^1.28.0, and several require-dev packages are updated (fruitcake/laravel-debugbar to ^4.3.0, laravel/boost to ^2.4.9, laravel/sail to ^1.62.0).

Possibly related PRs

• he4rt/heartdevs.com#180: Updates composer.json dependency versions including laravel/boost and laravel/sail.

Suggested reviewers

• danielhe4rt

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes both main changes: removing unused view loading from service providers and updating dependency versions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

composer.json (1)

36-36: ⚡ Quick win

Confirm VCS commit pin is valid (laracord/framework)

composer.json pins laracord/framework to dev-next#e7b64d6; the commit resolves to e7b64d62a09b7c197bcccf6e159b6fcb142ced29 (“chore: pin tinker-zero and fix composer formatting (#2)”), so the hash is present. Pinning to a commit still prevents automatic updates (including security fixes), so ensure this tradeoff is intentional and that you have a plan to update when needed.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@composer.json` at line 36, composer.json pins the dependency
"laracord/framework" to a specific commit (dev-next#e7b64d6) which prevents
automatic updates; verify that the commit hash resolves correctly (it does) and
then either replace the commit pin with a maintained version constraint or add a
short project-maintenance plan: (a) change "laracord/framework" to a semver tag
or branch (e.g., a release like "1.x" or "dev-next" without the commit) if you
want automatic updates, or (b) keep the commit pin but document in your project
README or dependency policy when and how you'll re-pin/update (including
security patch cadence) so the tradeoff is intentional; refer to the dependency
key "laracord/framework" in composer.json and update accordingly.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@composer.json`:
- Line 36: composer.json pins the dependency "laracord/framework" to a specific
commit (dev-next#e7b64d6) which prevents automatic updates; verify that the
commit hash resolves correctly (it does) and then either replace the commit pin
with a maintained version constraint or add a short project-maintenance plan:
(a) change "laracord/framework" to a semver tag or branch (e.g., a release like
"1.x" or "dev-next" without the commit) if you want automatic updates, or (b)
keep the commit pin but document in your project README or dependency policy
when and how you'll re-pin/update (including security patch cadence) so the
tradeoff is intentional; refer to the dependency key "laracord/framework" in
composer.json and update accordingly.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro

Run ID: fb865e5b-4696-475a-b3d4-c5e4b7eb550b

📥 Commits

Reviewing files that changed from the base of the PR and between 01f60a2 and 1b8b8fd.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• app-modules/events/src/EventsServiceProvider.php
• app-modules/identity/src/IdentityServiceProvider.php
• composer.json

💤 Files with no reviewable changes (2)

• app-modules/events/src/EventsServiceProvider.php
• app-modules/identity/src/IdentityServiceProvider.php

[thalesmengue]

😱