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

[py] Update dependency debugpy to v1.8.11 #14730

Merged
merged 2 commits into from
Dec 27, 2024
Merged

[py] Update dependency debugpy to v1.8.11 #14730

merged 2 commits into from
Dec 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
debugpy (source) ==1.8.7 -> ==1.8.11 age adoption passing confidence

Release Notes

microsoft/debugpy (debugpy)

v1.8.11: debugpy v1.8.11

Compare Source

Full Changelog: microsoft/debugpy@v1.8.9...v1.8.11

Fixes for:

v1.8.10

Compare Source

v1.8.9: debugpy v1.8.9

Compare Source

Fixes for:

v1.8.8: debugpy v1.8.8

Compare Source

Fixes for:


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 added the dependencies Pull requests that update a dependency file label Nov 8, 2024
@renovate renovate bot force-pushed the renovate/debugpy-1.x branch from c579192 to b415413 Compare November 9, 2024 15:11
Copy link
Contributor

qodo-merge-pro bot commented Nov 9, 2024

CI Failure Feedback 🧐

(Checks updated until commit a2062c1)

Action: Python / Build / Build

Failed stage: Pull latest changes [❌]

Failed test name: ""

Failure summary:

The action failed because Git encountered a merge conflict and couldn't automatically determine how
to reconcile divergent branches. This typically happens when:

  • The PR branch is out of sync with the target branch
  • Git needs explicit instructions on how to handle the merge strategy (rebase vs merge)
    The error
    suggests configuring Git's pull strategy using either git config pull.rebase true or git config
    pull.ff only

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    164:  hint:   git config pull.rebase true   # rebase
    165:  hint:   git config pull.ff only       # fast-forward only
    166:  hint:
    167:  hint: You can replace "git config" with "git config --global" to set a default
    168:  hint: preference for all repositories. You can also pass --rebase, --no-rebase,
    169:  hint: or --ff-only on the command line to override the configured default per
    170:  hint: invocation.
    171:  fatal: Need to specify how to reconcile divergent branches.
    172:  ##[error]Process completed with exit code 128.
    

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

    @renovate renovate bot changed the title chore(deps): update dependency debugpy to v1.8.8 Update dependency debugpy to v1.8.8 Nov 15, 2024
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from b415413 to 517a4bb Compare November 21, 2024 13:04
    Copy link

    codecov bot commented Nov 21, 2024

    Codecov Report

    All modified and coverable lines are covered by tests ✅

    Project coverage is 59.24%. Comparing base (b1828bf) to head (9b5e310).
    Report is 2 commits behind head on trunk.

    Additional details and impacted files
    @@           Coverage Diff           @@
    ##            trunk   #14730   +/-   ##
    =======================================
      Coverage   59.24%   59.24%           
    =======================================
      Files          94       94           
      Lines        6004     6004           
      Branches      268      268           
    =======================================
      Hits         3557     3557           
      Misses       2179     2179           
      Partials      268      268           

    ☔ View full report in Codecov by Sentry.
    📢 Have feedback on the report? Share it here.


    🚨 Try these New Features:

    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from 517a4bb to 9b5e310 Compare November 21, 2024 23:06
    @renovate renovate bot changed the title Update dependency debugpy to v1.8.8 Update dependency debugpy to v1.8.9 Nov 21, 2024
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from 9b5e310 to a41f7b6 Compare November 22, 2024 03:43
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from a41f7b6 to b2aa846 Compare December 11, 2024 00:29
    @renovate renovate bot changed the title Update dependency debugpy to v1.8.9 Update dependency debugpy to v1.8.10 Dec 11, 2024
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from b2aa846 to 08da3c9 Compare December 11, 2024 16:09
    @renovate renovate bot changed the title Update dependency debugpy to v1.8.10 Update dependency debugpy to v1.8.9 Dec 11, 2024
    @renovate renovate bot changed the title Update dependency debugpy to v1.8.9 Update dependency debugpy to v1.8.11 Dec 13, 2024
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from 08da3c9 to bbd546d Compare December 13, 2024 18:55
    @renovate renovate bot added the C-py label Dec 19, 2024
    @renovate renovate bot changed the title Update dependency debugpy to v1.8.11 [py] Update dependency debugpy to v1.8.11 Dec 19, 2024
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from bbd546d to e3da406 Compare December 27, 2024 00:08
    @renovate renovate bot force-pushed the renovate/debugpy-1.x branch from 34a5d06 to 299e1b1 Compare December 27, 2024 00:27
    @diemol diemol merged commit afb6e99 into trunk Dec 27, 2024
    1 check passed
    @diemol diemol deleted the renovate/debugpy-1.x branch December 27, 2024 00:46
    sandeepsuryaprasad pushed a commit to sandeepsuryaprasad/selenium that referenced this pull request Dec 27, 2024
    * [py] Update dependency debugpy to v1.8.11
    
    * Repin dependencies
    
    ---------
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Selenium CI Bot <[email protected]>
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    C-py dependencies Pull requests that update a dependency file
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants