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

merge main back into develop #63

Merged
merged 4 commits into from
Dec 4, 2024
Merged

merge main back into develop #63

merged 4 commits into from
Dec 4, 2024

Conversation

floriankrb
Copy link
Member

This does not change any code.

Apparently, the tag 0.4.9 needs to be in the ancestors of develop in order to be able to pip install ./anemoi-utils with the right version number.

Currently, doing pip install -e ./anemoi-utilsinstalls the right code but with a version number as 0.4.6+.... This makes pip to complain about version conflict issues when a package is requesting anemoi-utils version >= 0.4.9.

(In the future, the tag may need to be put on the develop branch, or this merge back to main should be automated.)

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.86%. Comparing base (2837ecd) to head (c3d3283).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #63   +/-   ##
========================================
  Coverage    71.86%   71.86%           
========================================
  Files            7        7           
  Lines          263      263           
========================================
  Hits           189      189           
  Misses          74       74           

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

@floriankrb floriankrb merged commit f9f35cb into develop Dec 4, 2024
111 checks passed
@floriankrb floriankrb deleted the main branch December 4, 2024 12:40
@JesperDramsch JesperDramsch restored the main branch December 13, 2024 14:11
@JesperDramsch JesperDramsch added the no changelog Flag a PR as not requiring a changelog update label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changelog Flag a PR as not requiring a changelog update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants