Repository navigation
chore: synchronize fork main with upstream #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 250 commits
00b4c49
11082f6
edf8e5d
fb0fc7e
7ef4187
4fbb253
57c60f2
3429670
8d4b741
bcef8d6
5d4f76b
be633b2
a39067f
1e65d6d
8db9f49
d0081d9
b4464f6
8c2f308
11ca36e
c573e62
4270e9a
cf12224
2b9e421
85d25f3
99fb18d
d538f4e
97f74b8
1bd7364
b3778db
ca812ba
a662f9d
02aa4b5
00bb169
f83ff89
e3ba651
5cf8d74
0922931
a504202
6c0750e
f914c9b
0d86694
7798241
1d5d059
1481a0d
f597c31
34e512a
23a4bd8
9c53128
8ed86c0
68837c5
d79575c
c4cbd7a
2bd6fe0
5f02693
a275ade
65f033a
9797679
4dcdb5e
eb027a8
c06caad
0237fcc
52ce7b2
9a78d5a
3329b38
f4f691c
fd3565d
27f32bd
3d8c492
fe04d5b
afcd5ea
b292e2d
50d7a75
12891ea
026e3e8
6927ff8
49fc491
75fbefa
14b9b93
9fc80ac
0b33913
c89f3b8
ae9cd70
26ed08c
1f92ab1
f17f18c
45c7388
d70fb4e
10b0722
55c223e
05315a6
f2c3455
c22588b
2019c0a
f986a2b
76de6ec
727c2d7
4cc42e6
22a03c8
b40998b
3fcbf13
e033bba
e3ff3e7
a4f2e42
84bbf17
cb1a42d
f845f02
78e0d29
6504f33
ae4f777
fb2f66f
68b16aa
2efb8bd
fc70d05
0746484
61d690a
9745a7f
5dfea72
258fa97
b578261
6495009
2d52ddc
f9d0508
478d772
0461da8
9d576c4
97fb475
7d50f99
d9833c5
af21210
12ad29a
53221df
b86fb27
1a4bb74
32a59f3
de25786
f087cb8
c13c37a
134b173
bdf45ab
b14315a
07ddfaa
7d44fe9
bbbccd3
7a5fc1b
1491342
5904c7a
a9ef4a7
cd0b5b9
a745101
1eb1b79
42da1f2
7072670
99f7d2b
4f54a6d
283e677
04767e7
b4e2ae9
62f64ae
9da8c63
ab1a6d0
7876d18
ab98a92
8aaf1ac
549e6aa
e3710c1
e1a1615
db529aa
bbbcde8
2a980fb
6ab2245
bb12ee7
08f2c78
50cd119
89c85b8
03c20ba
9f0bf22
9197afe
3a42722
a460b44
f5afe8b
965f18b
f94307a
a46ddf0
92f4246
5f88f0e
37fb7ad
3bc8395
5695ebc
b72e373
6339554
1770825
fbed1d4
0522ae9
1735ccd
9af6e9f
ada8e50
7f80efc
39ed610
ff17551
93af3db
35104c2
a7198a8
2c315ff
c990017
5a82258
850680f
3825d25
17c7be1
299d868
328542d
fdb76ce
170a736
b685299
e583d68
f850bc5
2337570
c5ff900
ab2f460
2f1609a
c54de79
284b303
e9bccc9
610c869
03f3b09
c81555e
48e3fb7
1022e48
979156b
0b54ebb
a5bbf43
8763d5b
441072a
0740753
62e2569
250ba18
5840f18
b0db7ea
ce7e81d
dfdd0ce
148ce16
4da9713
e6c068c
87d46b6
3480079
ddc08a9
fe32a31
d3f4bbc
ca23da8
8f1916f
160a5ff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| name: Case Collision Check | ||
|
|
||
| # Rejects PRs that track two files whose paths differ only by case | ||
| # (README.md vs readme.md, src/Foo.py vs SRC/foo.py). | ||
| # | ||
| # Linux is case-sensitive; Windows and macOS (default) are not. A | ||
| # case-colliding pair lives fine in a Linux checkout and silently breaks | ||
| # every clone on a case-insensitive host — the filesystem can hold only | ||
| # one of them, so checkout fails or whichever wins overwrites the other. | ||
| # Git won't prevent the pair from landing (it only warns at checkout time, | ||
| # on a case-insensitive FS, for the client doing the checkout), so the only | ||
| # enforcement point is CI, on Linux, against the index. | ||
| # | ||
| # Runs unconditionally (no change-classifier gate): a collision can ship in | ||
| # any kind of PR — docs, JS, config, not just Python — so gating on a | ||
| # language lane would be the same "passive rule that cannot enforce a | ||
| # policy" trap the infographic check exists to close. | ||
|
|
||
| on: | ||
| workflow_call: | ||
|
|
||
| permissions: | ||
| contents: read | ||
|
|
||
| jobs: | ||
| check-case-collisions: | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 5 | ||
| steps: | ||
| - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 | ||
|
|
||
| - name: Run case-collision checker | ||
| run: python3 scripts/check-case-collisions.py |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,7 +15,8 @@ name: OSV-Scanner | |
| # dep became known-vulnerable" case. | ||
| # | ||
| # Uses Google's officially-recommended reusable workflow, pinned by SHA. | ||
| # Findings land in the repo's Security tab (Code Scanning > OSV-Scanner). | ||
| # Findings land in the repo's Security tab for scheduled/main scans. PR scans | ||
| # keep the artifact and unified review status without creating a baseline-mismatch check. | ||
| # fail-on-vuln is disabled so the job does not block merges on pre-existing | ||
| # vulnerabilities in pinned deps that we may need to patch deliberately. | ||
| # | ||
|
|
@@ -25,6 +26,12 @@ name: OSV-Scanner | |
|
|
||
| on: | ||
| workflow_call: | ||
| inputs: | ||
| upload-sarif: | ||
| description: "Upload SARIF to Code Scanning (disabled for PR baseline mismatch)" | ||
| type: boolean | ||
| required: false | ||
| default: true | ||
| schedule: | ||
| # Weekly scan against main — catches CVEs published after merge for | ||
| # deps that haven't changed since. | ||
|
|
@@ -40,7 +47,7 @@ permissions: | |
| jobs: | ||
| scan: | ||
| name: Scan lockfiles | ||
| uses: google/osv-scanner-action/.github/workflows/osv-scanner-reusable.yml@9a498708959aeaef5ef730655706c5a1df1edbc2 # v2.3.8 | ||
| uses: google/osv-scanner-action/.github/workflows/osv-scanner-reusable.yml@baa4139e56d6312335d899e6ba045fa16d1d3d0b # v2.5.1 | ||
| with: | ||
| # Scan explicit lockfiles rather than recursing, so we only look at | ||
| # the five sources of truth and skip vendored / test / worktree dirs. | ||
|
|
@@ -53,6 +60,7 @@ jobs: | |
| # The upstream reusable workflow uploads this exact file under its | ||
| # fixed artifact name, which the wrapper downloads below. | ||
| results-file-name: osv-results.sarif | ||
| upload-sarif: ${{ inputs.upload-sarif }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When this workflow runs from its own weekly Useful? React with 👍 / 👎. |
||
| fail-on-vuln: false | ||
|
|
||
| emit-status: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| name: Profile Artifact Boundary | ||
|
|
||
| # A reusable, unconditional guard for the incident class in #92457. Ignore | ||
| # files reduce accidental staging; this job is the enforcement boundary that | ||
| # still catches `git add -f` and generated files present during a build. | ||
|
|
||
| on: | ||
| workflow_call: | ||
|
|
||
| permissions: | ||
| contents: read | ||
|
|
||
| jobs: | ||
| check-profile-artifacts: | ||
| name: Reject profile archives | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 5 | ||
| steps: | ||
| - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 | ||
| - name: Reject profile exports in the checkout | ||
| run: python3 scripts/ci/check_profile_archive_boundary.py |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
ci.yamlworkflow runs for both pull requests and pushes tomain, but this reusable-workflow call unconditionally passesupload-sarif: false. Consequently, the post-merge OSV scan also suppresses Code Scanning publication, even though the adjacent comment says the workaround is for PR runs; onmainthere is no PR review consumer, and the remaining short-lived artifact is not a durable alert. Passfalseonly whengithub.event_name == 'pull_request'so main-push scans retain SARIF.Useful? React with 👍 / 👎.