-
Notifications
You must be signed in to change notification settings - Fork 0
44 lines (40 loc) · 1.51 KB
/
Copy pathdev-staleness.yml
File metadata and controls
44 lines (40 loc) · 1.51 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# Generated-artifact staleness gates on dev pushes.
#
# The full .NET 10 workflow runs only on mainline pushes/PRs, so a batch landing on dev
# can carry stale (or never-successfully-regenerated) spy-sourced C# undetected until the
# mainline push — which is exactly how the #1607 re.I break shipped: the spy-test regen
# had been failing since mid-batch and nothing on dev ran it. This workflow runs just the
# build and the two staleness gates (~a few minutes) on every dev push that could affect
# generated artifacts. Content mirrors the "Verify .spy * staleness" steps in dotnet10.yml.
name: Dev Staleness Gates
on:
push:
branches: [ "dev" ]
paths:
- 'src/**'
- 'Directory.Build.props'
- 'sharpy.sln'
- 'build_tools/regenerate_spy_stdlib.sh'
- 'build_tools/regenerate_spy_tests.sh'
- 'build_tools/check_spy_staleness.sh'
- 'build_tools/check_spy_tests_staleness.sh'
- '.github/workflows/dev-staleness.yml'
jobs:
staleness:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@v7
- name: Setup .NET
uses: actions/setup-dotnet@v6
with:
dotnet-version: 10.0.x
- name: Restore dependencies
run: dotnet restore sharpy.sln
- name: Build compiler CLI
run: dotnet build src/Sharpy.Cli --no-restore
- name: Verify .spy stdlib C# staleness
run: bash build_tools/check_spy_staleness.sh
- name: Verify .spy test C# staleness
run: bash build_tools/check_spy_tests_staleness.sh