Bump laravel/pint from 1.18.3 to 1.19.0

[dependabot]

Bumps laravel/pint from 1.18.3 to 1.19.0.

Release notes

Sourced from laravel/pint's releases.

v1.19.0

• Adds single_line_comment_spacing rule. laravel/pint#315
• Ignores PHP 8.4 deprecations. laravel/pint#319

Changelog

Sourced from laravel/pint's changelog.

v1.19.0 - 2024-12-30

• Adds single_line_comment_spacing rule. laravel/pint#315
• Ignores PHP 8.4 deprecations. laravel/pint#319

Commits

• 8169513 Release 1.19.0
• 2128bf5 Bumps dependencies
• 6857eef Merge pull request #322 from laravel/fix/removes-warning
• 6945563 Merge pull request #321 from laravel/feat/bumps-deps
• 5a62e34 Removes warning
• d33bd49 Bumps dependencies
• 854039c Hides PHP 8.4 Deperecation Warning (#319)
• fecb306 Add single_line_comment_spacing rule (#315)
• 43a25d9 Show warning regarding PHP 8.4 support (#312)
• fc6a920 Update CHANGELOG
• See full diff 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Update laravel/pint from 1.18.3 to 1.19.0.

New Features:

• Add the single_line_comment_spacing rule.

Tests:

• Ignore PHP 8.4 deprecations.

[dependabot]

The following labels could not be found: php, composer, dependencies.

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[semanticdiff-com]

Review changes with  

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR bumps the version of laravel/pint from 1.18.3 to 1.19.0. It introduces a new rule for single-line comment spacing and addresses PHP 8.4 deprecations.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Adds a new rule for single-line comment spacing.	The single_line_comment_spacing rule is introduced to enforce consistent spacing in single-line comments.	composer.lock
Addresses PHP 8.4 deprecations.	Code updated to handle PHP 8.4 deprecations, ensuring compatibility with newer PHP versions.	composer.lock
Bumps dependencies.	Updates project dependencies to their latest versions to benefit from bug fixes, performance improvements, and new features.	composer.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[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.
  • 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. (Beta)
• @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.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[instapr]

Feedback:

• ✅ Bumped laravel/pint from 1.18.3 to 1.19.0.
• ✅ Updated friendsofphp/php-cs-fixer to ^3.66.0.
• ✅ Updated illuminate/view to ^10.48.25.
• ✅ Updated larastan/larastan to ^2.9.12.
• ✅ Updated laravel-zero/framework to ^10.48.25.

This PR looks good. Thank you for the update!

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. Composer Dependency Increasing:

   • composer.lock - Updating dependencies to their latest versions (e.g., upgrading laravel/pint from v1.18.3 to v1.19.0) may lead to incompatibility with the existing codebase if there are significant breaking changes. Ensure compatibility testing is done post-update, including verification against existing tests.

2. Version Pinning Risks:

   • composer.lock - The upgraded versions (e.g., friendsofphp/php-cs-fixer to ^3.66.0) can introduce new linting rules or modify existing ones. This can create unexpected issues within the code quality checks, particularly if local coding practices rely on older behavior.

3. Potentially Incorrect time Field:

   • composer.lock - Updating the "time" to "2024-12-30T16:20:10+00:00" appears to be a future date based on the current context. If this package version is not intended to be released at that time, it could mislead developers about the age of the package or indicate instability.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. Review for Compatibility:

   • composer.lock - Conduct a detailed review of changelogs for each updated package. Document any breaking changes or required updates to your codebase to ensure smooth integration, including regression testing.

2. Testing Procedures:

   • composer.lock - Implement or enhance your Continuous Integration (CI) process to automatically run tests against the updated dependencies. This helps catch any incompatibilities or issues early in the development process.

3. Lock File Management:

   • composer.lock - Regularly update and test your composer.lock file to keep dependencies manageable and up to date. Establish a routine (e.g., monthly or quarterly) to reassess dependencies and ensure they're kept in sync with the codebase needs without accumulating unnecessary risks.

[deepsource-io]

Here's the code health analysis summary for commits dd76727..001a9a2. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
SQL	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Php
Branch Coverage	100%	100%
Composite Coverage	33.3%	33.3%
Line Coverage	33.3%	33.3%

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

7:26PM INF scanning for exposed secrets...
7:26PM INF 167 commits scanned.
7:26PM INF scan completed in 415ms
7:26PM INF no leaks found