1
0

Enable publishing with fixed version

Former-commit-id: 751ed2e1570ed8da1031c9675469251d68e13a88
This commit is contained in:
David Boreham 2023-04-09 22:41:01 -06:00 committed by GitHub
parent 8fb9e6d39b
commit fe77955845

View File

@ -6,15 +6,9 @@ on:
push:
branches: '*'
# Enable debug logging
env:
ACTIONS_STEP_DEBUG: true
RUNNER_DEBUG: true
ACTIONS_RUNNER_DEBUG: true
jobs:
test:
name: "Build"
publish:
name: "Build and publish"
runs-on: ubuntu-latest
steps:
- name: "Clone project repository"
@ -28,19 +22,27 @@ jobs:
- name: "Install shiv"
run: pip install shiv
- name: "Create release"
uses: cerc-io/action-gh-release@v1
uses: cerc-io/action-gh-release@gitea-v1
# We haven't decided how to trigger this release job.
# It might be done on creation of a git tag
# Or it might be done on merge to a release branch
# Somehow by this point however we need to know the release version
with:
tag_name: "v1.2.4"
tag_name: "v1.2.5"
- name: "Build local shiv package"
id: build
# Build has to be done after deciding on the version because
# we bundle the version into the build
run: ./scripts/build_shiv_package.sh
run: |
./scripts/build_shiv_package.sh
result_code=$?
echo "::set-output name=package-file::$(ls ./package/*)"
exit $result_code
- name "Stage artifact file"
run: |
cp ${{ steps.build.outputs.package-file }} ./laconic-so
- name: "Upload release artifact"
uses: cerc-io/action-gh-release@v1
uses: cerc-io/action-gh-release@gitea-v1
with:
tag_name: "v1.2.4"
files: requirements.txt
tag_name: "v1.2.5"
files: ./laconic-so