MindWorkAI/AI-Studio
MindWorkAI/AI-Studio
1
0
Fork 0
mirror of https://github.com/MindWorkAI/AI-Studio.git synced 2025-04-28 15:39:46 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fixed comment placement for cache key explanation

Browse Source
This commit is contained in:
Thorsten Sommer 2024-06-09 15:28:43 +02:00
parent b9d9e3914d
commit 0678428fab
Signed by: tsommer
GPG Key ID: 371BBA77A02C0108
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
.github/workflows/build-and-release.yml vendored
View File

@ -102,14 +102,14 @@ jobs:
# When the entire key matches, Rust might just create the bundles using the current .NET build: # When the entire key matches, Rust might just create the bundles using the current .NET build:
key: target-${{ matrix.dotnet_runtime }}-rust-${{ env.RUST_VERSION }}-dependencies-${{ env.CARGO_LOCK_HASH }} key: target-${{ matrix.dotnet_runtime }}-rust-${{ env.RUST_VERSION }}-dependencies-${{ env.CARGO_LOCK_HASH }}
restore-keys: | # - 1st key: the Rust runtime dependencies changed. Anyway, we might be able to re-use many previously built packages.
# The Rust runtime dependencies changed. Anyway, we might be able to re-use many previously built packages: #
target-${{ matrix.dotnet_runtime }}-rust-${{ env.RUST_VERSION }}-dependencies- # - No match: alright, a new Rust version was released. Sadly, we cannot re-use anything now. Why?
# Alright, a new Rust version was released. Sadly, we cannot re-use anything now. Why?
# The updated Rust compiler might mitigate some bugs or vulnerabilities. In order to apply # The updated Rust compiler might mitigate some bugs or vulnerabilities. In order to apply
# these changes to our app, we have to re-compile everything. Thats the reason, why it makes # these changes to our app, we have to re-compile everything. That's the reason why it makes
# no sense to use more parts for the cache key, like Tauri or Tauri build versions. # no sense to use more parts for the cache key, like Tauri or Tauri build versions.
restore-keys: |
target-${{ matrix.dotnet_runtime }}-rust-${{ env.RUST_VERSION }}-dependencies-
- name: Setup Rust (stable) - name: Setup Rust (stable)
uses: dtolnay/rust-toolchain@stable uses: dtolnay/rust-toolchain@stable
@ -233,14 +233,14 @@ jobs:
# When the entire key matches, Rust might just create the bundles using the current .NET build: # When the entire key matches, Rust might just create the bundles using the current .NET build:
key: target-linux-arm-rust-${{ env.RUST_VERSION }}-dependencies-${{ env.CARGO_LOCK_HASH }} key: target-linux-arm-rust-${{ env.RUST_VERSION }}-dependencies-${{ env.CARGO_LOCK_HASH }}
restore-keys: | # - 1st key: the Rust runtime dependencies changed. Anyway, we might be able to re-use many previously built packages.
# The Rust runtime dependencies changed. Anyway, we might be able to re-use many previously built packages: #
target-linux-arm-rust-${{ env.RUST_VERSION }}-dependencies- # - No match: alright, a new Rust version was released. Sadly, we cannot re-use anything now. Why?
# Alright, a new Rust version was released. Sadly, we cannot re-use anything now. Why?
# The updated Rust compiler might mitigate some bugs or vulnerabilities. In order to apply # The updated Rust compiler might mitigate some bugs or vulnerabilities. In order to apply
# these changes to our app, we have to re-compile everything. Thats the reason, why it makes # these changes to our app, we have to re-compile everything. That's the reason why it makes
# no sense to use more parts for the cache key, like Tauri or Tauri build versions. # no sense to use more parts for the cache key, like Tauri or Tauri build versions.
restore-keys: |
target-linux-arm-rust-${{ env.RUST_VERSION }}-dependencies-
- name: Build linux arm runner image - name: Build linux arm runner image
uses: pguyot/arm-runner-action@v2.6.5 uses: pguyot/arm-runner-action@v2.6.5