v0.7.3#1017
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
How to release
A short primer in the steps needed to release a new version of the
weldxpackagecreate release PR
vX.Y.Zand add thereleasetag (example here)
CHANGELOG.mdis up-to-date and enter current date to the release versionCITATION.cffversion number and datedeprecatedand remove deprecated codeMerge the Pull Request
add Git(hub) tag
doubt use vX.Y.Z everywhere)
ReadTheDocs updates
latest,stableandvX.Y.Zget triggered on RTD (the tag build can gettriggered twice, resulting in a failed/duplicated build, no need to worry)
pypi release
buildaction completes hereconda-forge release
pull-request here
meta.yamlin the pull request, manually update all changes in the build and run dependencies