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

chore(deps): update selenium/node-firefox docker tag to v131 #2426

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 10, 2024

This PR contains the following updates:

Package Update Change
selenium/node-firefox major 4.25.0-20241024 -> 131.0.3-20241024

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.

@renovate renovate bot changed the title chore(deps): update selenium/node-firefox docker tag to v131 chore(deps): update selenium/node-firefox docker tag to v131 - autoclosed Oct 24, 2024
@renovate renovate bot closed this Oct 24, 2024
@renovate renovate bot deleted the renovate/selenium-node-firefox-131.x branch October 24, 2024 11:12
@renovate renovate bot changed the title chore(deps): update selenium/node-firefox docker tag to v131 - autoclosed chore(deps): update selenium/node-firefox docker tag to v131 Oct 24, 2024
@renovate renovate bot restored the renovate/selenium-node-firefox-131.x branch October 24, 2024 14:00
@renovate renovate bot reopened this Oct 24, 2024
@renovate renovate bot force-pushed the renovate/selenium-node-firefox-131.x branch from 10d8fc4 to 8c8c740 Compare October 24, 2024 14:00
Copy link

codiumai-pr-agent-pro bot commented Oct 24, 2024

CI Failure Feedback 🧐

(Checks updated until commit 8c8c740)

Action: Rerun workflow when failure

Failed stage: Authenticate GitHub CLI for PR [❌]

Failure summary:

The action failed due to an authentication error with the GitHub CLI:

  • The token used for authentication is missing the required scope read:org.
  • This missing scope prevents the gh auth login command from successfully validating the token.
  • As a result, the process completed with exit code 1, indicating failure.

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    28:  SecurityEvents: write
    29:  Statuses: write
    30:  ##[endgroup]
    31:  Secret source: Actions
    32:  Prepare workflow directory
    33:  Prepare all required actions
    34:  Getting action download info
    35:  Download action repository 'actions/checkout@main' (SHA:11bd71901bbe5b1630ceea73d27597364c9af683)
    36:  Complete job name: Rerun workflow when failure
    ...
    
    48:  show-progress: true
    49:  lfs: false
    50:  submodules: false
    51:  set-safe-directory: true
    52:  env:
    53:  GH_CLI_TOKEN: ***
    54:  GH_CLI_TOKEN_PR: ***
    55:  RUN_ID: 11500902672
    56:  RERUN_FAILED_ONLY: true
    ...
    
    119:  ##[group]Run sudo apt update
    120:  �[36;1msudo apt update�[0m
    121:  �[36;1msudo apt install gh�[0m
    122:  shell: /usr/bin/bash -e {0}
    123:  env:
    124:  GH_CLI_TOKEN: ***
    125:  GH_CLI_TOKEN_PR: ***
    126:  RUN_ID: 11500902672
    127:  RERUN_FAILED_ONLY: true
    ...
    
    168:  0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
    169:  ##[group]Run echo "$GH_CLI_TOKEN_PR" | gh auth login --with-token
    170:  �[36;1mecho "$GH_CLI_TOKEN_PR" | gh auth login --with-token�[0m
    171:  shell: /usr/bin/bash -e {0}
    172:  env:
    173:  GH_CLI_TOKEN: ***
    174:  GH_CLI_TOKEN_PR: ***
    175:  RUN_ID: 11500902672
    176:  RERUN_FAILED_ONLY: true
    177:  RUN_ATTEMPT: 1
    178:  ##[endgroup]
    179:  error validating token: missing required scope 'read:org'
    180:  ##[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.

    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