guanguans / favorite-link

❤️ 每天收集喜欢的开源项目。
https://www.guanguans.cn/favorite-link/
GNU General Public License v3.0
2.75k stars 259 forks source link

build(deps-dev): bump phpstan/phpstan from 1.12.4 to 1.12.5 #122

Closed dependabot[bot] closed 4 weeks ago

dependabot[bot] commented 4 weeks ago

Bumps phpstan/phpstan from 1.12.4 to 1.12.5.

Release notes

Sourced from phpstan/phpstan's releases.

1.12.5

Improvements 🔧

Bugfixes 🐛

Function signature fixes 🤖

Internals 🔍

Commits
  • 7e6c6cb PHPStan 1.12.5
  • 5ff4cab Updated PHPStan to commit 5ff4cab1296b9a447bb1e39de601208a80733e9b
  • 23c53a2 Updated PHPStan to commit 23c53a2210b715f672ad3087dd476faf34bdec6e
  • 714877b Updated PHPStan to commit 714877be8cafc1ba08610929e4dcb0d43273cc8d
  • c83196b Updated PHPStan to commit c83196bef4ab9f48591c25d2a216c90b51fa6740
  • fd304ca Updated PHPStan to commit fd304ca33f9653bdb30b3f6a4f1cddaed34c7343
  • ae53f11 Updated PHPStan to commit ae53f11329d9203dd4ac83df2d7338ed1a4c2d83
  • 9f13233 Updated PHPStan to commit 9f13233ec7c1caa6554867ca5be63552e5914ec9
  • 31362eb Updated PHPStan to commit 31362eb1971a0d408bf4565da077397adaa0733f
  • 18196e9 Updated PHPStan to commit 18196e9ec47ef933cb65a7e97d2b37d7ecc4518b
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
update-docs[bot] commented 4 weeks ago

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would update some of our documentation based on your changes.

codiumai-pr-agent-pro[bot] commented 4 weeks ago

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

**Action:** dependabot
**Failed stage:** [Auto-merge Dependabot PRs for semver-patch updates](https://github.com/guanguans/favorite-link/actions/runs/11060529498/job/30731252446) [❌]
**Failure summary:** The action failed because the attempt to automatically merge the pull request was unsuccessful.
  • The error message indicates that the branch does not have protected branch rules configured to allow
    auto-merging.
  • Specifically, the enablePullRequestAutoMerge setting is not enabled for this branch.
  • Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ... 49: ##[group]Run gh pr merge --auto --merge "$PR_URL" 50: gh pr merge --auto --merge "$PR_URL" 51: shell: /usr/bin/bash -e {0} 52: env: 53: PR_URL: https://github.com/guanguans/favorite-link/pull/122 54: GITHUB_TOKEN: *** 55: ##[endgroup] 56: GraphQL: Pull request Protected branch rules not configured for this branch (enablePullRequestAutoMerge) 57: ##[error]Process completed with exit code 1. ```

    ✨ CI feedback usage guide:
    The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).
    codiumai-pr-agent-pro[bot] commented 4 weeks ago

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    **Action:** to_gitlab
    **Failed stage:** [Run pixta-dev/repository-mirroring-action@v1](https://github.com/guanguans/favorite-link/actions/runs/11060529026/job/30731251228) [❌]
    **Failure summary:** The log message does not provide enough information to determine why the action failed. It only
    indicates the operating system being used, which is Ubuntu. More detailed logs are needed to
    identify the cause of the failure.
    Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ```

    ✨ CI feedback usage guide:
    The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).