From 7f465cd2ee5ab313e9a2125ca3bdaeb5665877f2 Mon Sep 17 00:00:00 2001 From: rusefillc Date: Wed, 19 Jan 2022 22:09:37 -0500 Subject: [PATCH] Well, for release builds we want to build everything? #3817 ## January 2022 Release - "Tin Can" --- .github/workflows/build-firmware.yaml | 3 ++- firmware/CHANGELOG.md | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/workflows/build-firmware.yaml b/.github/workflows/build-firmware.yaml index 2a03be04c0..b1d16db4f4 100644 --- a/.github/workflows/build-firmware.yaml +++ b/.github/workflows/build-firmware.yaml @@ -195,7 +195,8 @@ jobs: steps: - name: Execution throttle early exit if: ${{ matrix.skip-rate }} - run: if (($(($RANDOM % 100)) < ${{ matrix.skip-rate }})); then echo "skip=true" >> $GITHUB_ENV; fi + # todo: how do we produce well-defined releases with skip-rate approach? For I can think of hacking the line below before a release + run: if (($(($RANDOM % 100)) < ${{ matrix.skip-rate }})); then echo "skip=not_true" >> $GITHUB_ENV; fi - uses: actions/checkout@v1 if: ${{ env.skip != 'true' }} diff --git a/firmware/CHANGELOG.md b/firmware/CHANGELOG.md index 53a2a65f1f..e9a7f26d8b 100644 --- a/firmware/CHANGELOG.md +++ b/firmware/CHANGELOG.md @@ -25,7 +25,7 @@ Release template (copy/paste this for new release): All notable user-facing or behavior-altering changes will be documented in this file. -## Month 202x Release - "Release Name" +## January 2022 Release - "Tin Can" ### Added - Per-cylinder fuel trim tables