Skip to content

release: prepare 0.3.9 customer hardening #3213

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.

Sign up for GitHub

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

Merged
oscharko merged 4 commits into from
Aug 18, 2026
Merged

release: prepare 0.3.9 customer hardening #3213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
96a7c49
release: prepare 0.3.9 customer hardening
oscharko Aug 18, 2026
a82868f
fix(ci): bound a branch-creating push's quality range at the head parent
oscharko Aug 18, 2026
4d9ee25
fix(ci): bound branch-creating pushes at the merge-base with dev
oscharko Aug 18, 2026
3c9b176
fix(ci): validate the fallback base ref shape and pin hostile inputs
oscharko Aug 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,13 @@ jobs:
env:
QUALITY_BASE_SHA: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before }}
QUALITY_HEAD_SHA: ${{ github.event.pull_request.head.sha || github.sha }}
run: node scripts/resolve-quality-range.mjs >> "$GITHUB_OUTPUT"
# A branch-creating push delivers the zero SHA as its before-pointer; the fallback ref
# bounds the range at the merge-base with dev so EVERY commit introduced by the branch
# creation is scanned (fetch-depth 0 clones only the triggering ref, hence the fetch).
QUALITY_FALLBACK_BASE_REF: origin/dev
run: |
git fetch --no-tags --quiet origin dev
node scripts/resolve-quality-range.mjs >> "$GITHUB_OUTPUT"
- name: Reject semantic clone groups introduced by this change
env:
QUALITY_BASE_SHA: ${{ steps.quality-range.outputs.base }}
Expand Down Expand Up @@ -188,7 +194,13 @@ jobs:
env:
QUALITY_BASE_SHA: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before }}
QUALITY_HEAD_SHA: ${{ github.event.pull_request.head.sha || github.sha }}
run: node scripts/resolve-quality-range.mjs >> "$GITHUB_OUTPUT"
# A branch-creating push delivers the zero SHA as its before-pointer; the fallback ref
# bounds the range at the merge-base with dev so EVERY commit introduced by the branch
# creation is scanned (fetch-depth 0 clones only the triggering ref, hence the fetch).
QUALITY_FALLBACK_BASE_REF: origin/dev
run: |
git fetch --no-tags --quiet origin dev
node scripts/resolve-quality-range.mjs >> "$GITHUB_OUTPUT"
- name: Reject secrets introduced anywhere in the pull-request history
env:
QUALITY_BASE_SHA: ${{ steps.quality-range.outputs.base }}
Expand Down
10 changes: 5 additions & 5 deletions .github/zizmor.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,12 +33,12 @@ rules:
# before removal: `zizmor` reports zero cache-poisoning findings for the pre-#2704 ci.yml with
# no ignore list at all.
# USearch runtime: coverage-packages, coverage-ui, coverage-scripts
- ci.yml:416
- ci.yml:506
- ci.yml:572
- ci.yml:428
- ci.yml:518
- ci.yml:584
# coverage-sonar: npm download cache (the one job that saves it), Sonar Scanner CLI archive
- ci.yml:651
- ci.yml:737
- ci.yml:663
- ci.yml:749
dangerous-triggers:
ignore:
# ADR-0161: the infrastructure-signature observer must see runs that have already completed, and
Expand Down
Loading
Loading