fix(ci): revise distribution scripts and workflow #1103
Merged
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.
Only trigger job to open PR reinitializing
develop
after release is published. The automated workflow only creates a draft release — the release must be published manually after inspection. Previously the reinitialization job was triggered immediately after the release branch was merged tomaster
, after this reinit will only happen after the release post is converted from draft to official.Update
develop
reinitialization job such that, for minor version releases, minor version number is incremented from just-released version and patch number is reset to 0, while for patch releases, the version ondevelop
does not change. This is according to the tentative expectation that minor version releases will branch fromdevelop
, while patch releases will branch frommaster
to exclude broader changesets in progress ondevelop
. The forthcoming6.4.1
release is an exception to the above:develop
will be bumped to6.5.0
after6.4.1
but will then stay there for all subsequent6.4.X
patches until6.5.0
is released.Run test suite after building binaries (tests should all pass before a release branch is created, but a final check is probably not a bad idea)
Fix
test_z01_testmodels_mf6.py
to skip dev testmodels/examples onv6*
branches, since this is how release branches must be named to trigger therelease.yml
workflow (previously only skipped on branches namedmaster
andrelease
)Add
developmode
test marker to skip tests requiringIDEVELOPMODE = 1
in the release workflowFix
update_version.py
minor/patch version increment flagsOnly build examples in
build_dist.py
for full release