This repository has been archived by the owner on Oct 11, 2021. It is now read-only.
ci: update requirements through GitHub Actions #412
Merged
Conversation
This file contains 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
|
e92dd1a (PAT) doesn't work yet |
redeboer
force-pushed
the
requirements-python-36-38
branch
from
ff02407
to
e40af6a
Compare
redeboer
force-pushed
the
requirements-python-36-38
branch
from
e40af6a
to
7a6b611
Compare
|
Ok seems that 7a6b611 does the job |
This was referenced Dec 17, 2020
redeboer
added a commit
to ComPWA/PWA-pages
that referenced
this pull request
Jan 16, 2021
* build: limit to sphinxcontrib-bibtex < 2 * ci: import dev dependency upgrader ComPWA/expertsystem#412 * ci: upgrade developer dependencies (automatic) * fix: cross-references in develop page
This was referenced Apr 14, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #409
Closes #402
Requirements differ for each version of Python. We therefore have to maintain
requirement.txtfiles for each version of Python that we supports. It is, however, hard to update these lists manually, so it is better to do this through a GitHub workflow (which has access to all versions of Python).See also
https://github.com/jazzband/pip-tools#cross-environment-usage-of-requirementsinrequirementstxt-and-pip-compile
requirements.txtfiles to different subfoldersdev/3.6,dev/3.7,dev/3.8in GitHub Actionsimportlib-resourcesandimportlib-metadatafor Python 3.6-3.7setup.cfgand*.infiles (git diffnon-empty) --> abac046 and f17f0d8skip-installandwhitelist_externalsintox--> 8c2c1e0environment.ymlfile --> 7f2a06ctox -e upgrade--> 0600b01setup.cfgandreqs✅ Works
redeboer/expertsystem-test-cron-job/pull/2✅ Works
redeboer/expertsystem-test-cron-job/pull/5https://github.com/redeboer/expertsystem-test-cron-job/actions/runs/426375571
✅ Works
https://github.com/redeboer/expertsystem-test-cron-job/runs/1565989056setup.cfgorreqs--> dce0460✅ Works
redeboer/expertsystem-test-cron-job/pull/6https://github.com/redeboer/expertsystem-test-cron-job/pull/6/checks?check_run_id=1566702836
✅ Works
redeboer/expertsystem-test-cron-job/pull/7https://github.com/redeboer/expertsystem-test-cron-job/actions/runs/426703151