Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency ch.qos.logback:logback-classic to v1.5.15 #2109

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ch.qos.logback:logback-classic (source, changelog) 1.5.14 -> 1.5.15 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

Copy link
Contributor

qodo-merge-pro bot commented Dec 21, 2024

CI Failure Feedback 🧐

(Checks updated until commit 1500f0d)

Action: tests (macos)

Failed stage: Install Edge for set binary test [❌]

Failure summary:

The action failed because it could not download Microsoft Edge (stable version) for macOS ARM64
architecture. The artifact was not found for this specific platform combination (darwin arm64).

Relevant error logs:
1:  ##[group]Operating System
2:  macOS
...

135:  edge-version: stable
136:  env:
137:  DISPLAY: :99
138:  GITHUB_TOKEN: ***
139:  GH_TOKEN: ***
140:  ##[endgroup]
141:  Setup Edge stable
142:  Attempting to download Edge stable...
143:  ##[error]Artifact not found of Edge stable for platform darwin arm64

✨ 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.

Copy link

netlify bot commented Dec 21, 2024

Deploy Preview for selenium-dev ready!

Name Link
🔨 Latest commit 1500f0d
🔍 Latest deploy log https://app.netlify.com/sites/selenium-dev/deploys/67670a0dfa24680008c6960d
😎 Deploy Preview https://deploy-preview-2109--selenium-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants