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

Adapt version migrator for recipe.yaml #2883

Closed
wants to merge 4 commits into from

Conversation

Hofer-Julian
Copy link
Contributor

No description provided.

@Hofer-Julian Hofer-Julian force-pushed the feat/version-migrator branch 2 times, most recently from 4540d89 to 9db0260 Compare August 1, 2024 13:32
Write recipe.yaml not meta.yaml

Add schema to recipe yaml

Prepare test for the adapted migrator

Adapt `update_build_number` for recipe.yaml

fix: function signature to match baseclass

Update version.py

refactor: Improve `test_version_cupy`

refactor: Improve "run_test_migration"
Copy link
Contributor Author

@Hofer-Julian Hofer-Julian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I leave these comments, so I or even better @wolfv can more easily pick up this PR later on.

A set of strings giving any errors found when updating the
version. The set will be empty if there were no errors.
"""
raise NotImplementedError()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This still needs to be implemented.
update_version the meta.yaml pendant contains a lot of logic. One has to have a close look which parts of it are not necessary for recipe.yaml and how to adapt the rest that is.

)

# these are here for legacy migrators
pmy["version"] = pmy["meta_yaml"]["package"]["version"]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function started out as a copy of run_test_migration the meta.yaml pendant. Only up to this point, I am fairly sure that nothing needs to be adapted anymore. The rest should be evaluated if it is needed or if it needs to be adapted.

for case in cases:
replace_build_number(recipe, *case)

return yaml.dump(recipe, sort_keys=False)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yaml sorts the keys per default when deserializing. I don't think we ever want that, so let's remember to set the argument also for other cases of yaml.dump in this and other PRs.

@Hofer-Julian
Copy link
Contributor Author

Closing in favor of #2920

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.

2 participants