Skip to content

[CI Bot] environment lockfiles auto-update #5605

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

Closed
wants to merge 1 commit into from

Conversation

scitools-ci[bot]
Copy link
Contributor

@scitools-ci scitools-ci bot commented Nov 25, 2023

Lockfiles updated to the latest resolvable environment.

If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.

@scitools-ci scitools-ci bot added Bot A bot generated issue/pull-request New: Pull Request labels Nov 25, 2023
Copy link

codecov bot commented Nov 25, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (507c34c) 89.68% compared to head (1652a34) 89.68%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5605   +/-   ##
=======================================
  Coverage   89.68%   89.68%           
=======================================
  Files          90       90           
  Lines       22815    22815           
  Branches     5445     5445           
=======================================
  Hits        20462    20462           
  Misses       1619     1619           
  Partials      734      734           

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

@rcomer
Copy link
Member

rcomer commented Nov 27, 2023

See also #5606, which could replace this.

@pp-mo pp-mo closed this in #5606 Nov 28, 2023
@rcomer rcomer deleted the auto-update-lockfiles branch November 28, 2023 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot A bot generated issue/pull-request New: Pull Request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants