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.
.gitlab-ci.yml
pyproject.yml
aioitertools==0.11.0
has been forgotten at the latest jade-PRrelease-helper.py
does no longer need theset_setup_py_version
command and theinstall_wheel
command was not usable in order to test the build locally. The new way of figuring out which version we're on is done fully automatically by setuptools_scm. It creates versionstrings viapython3 -m setuptools_scm
like2.0.4rc9.dev0+g72b1b9a9.d20240522
. Installing that needs something different that a fixed naming schemaThe failed build is only the "tag_specterext_dummy_repo" job which doesn't work in my gitlab fork which i used to test the release process. Iinstead of
git tag v2.0.4-pre8 && git push upstream v2.0.4-pre8
i usedgit tag v2.0.4-pre8 && git push origin v2.0.4-pre8
. This will trigger the sync to my personal gitlab fork which will in turn trigger the gitlab release to my github-fork: https://github.com/k9ert/specter-desktop/releases/tag/v2.0.4-pre8