mirror of
https://github.com/theupdateframework/python-tuf
synced 2026-05-24 10:08:28 +00:00
b6c3b66ca6
* don't autoupgrade pip: let's consider pip to be part of platform? * pin build and tox in new requirements-build.txt: this mostly prevents tox from going to 4.x before we're ready * use requirements-build.txt as constraint when installing tox or build during CI & CD * use requirements-build.txt in requiremenets-dev.txt Note that coveralls is not pinned, not sure if it should be. Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
36 lines
1.2 KiB
YAML
36 lines
1.2 KiB
YAML
on:
|
|
schedule:
|
|
- cron: "0 13 * * *"
|
|
workflow_dispatch:
|
|
|
|
name: Specification version check
|
|
|
|
permissions: {}
|
|
|
|
jobs:
|
|
# Get the version of the TUF specification the project states it supports
|
|
get-supported-tuf-version:
|
|
runs-on: ubuntu-latest
|
|
outputs:
|
|
version: ${{ steps.get-version.outputs.version }}
|
|
steps:
|
|
- uses: actions/checkout@93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8
|
|
- uses: actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984
|
|
with:
|
|
python-version: "3.x"
|
|
- id: get-version
|
|
run: |
|
|
python3 -m pip install -e .
|
|
script="from tuf.api.metadata import SPECIFICATION_VERSION; \
|
|
print(f\"v{'.'.join(SPECIFICATION_VERSION)}\")"
|
|
ver=$(python3 -c "$script")
|
|
echo "version=$ver" >> $GITHUB_OUTPUT
|
|
# Get the latest TUF specification release and open an issue (if needed)
|
|
specification-bump-check:
|
|
permissions:
|
|
contents: read
|
|
issues: write
|
|
needs: get-supported-tuf-version
|
|
uses: theupdateframework/specification/.github/workflows/check-latest-spec-version.yml@master
|
|
with:
|
|
tuf-version: ${{needs.get-supported-tuf-version.outputs.version}}
|