feat(make): add the emergency-release target to locally build and publish a new package release without Github Action workflows #544
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.
Closes #542
However, this new
make
target does not consider — in a way even duplicates! — how the Action workflows proceed. Unless we consider PR #537, trying to lower more workflow jobs into the Makefile would result in running checks and tests too often.Thought: should we make this target
python-package-template/Makefile
Line 210 in f8d7a18
dependent on
check test
(or justdist
) to ensure the package is alright?