You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 19a97e1
Browse filesBrowse the repository at this point in the historyBrowse files
"description": "Track the BuildKit SBOM scanner pinned by tag and digest in hack/common-envs.mk. The dockerfile manager does not read Makefiles and the helm-values manager is disabled repo-wide (see enabledManagers above), so without this manager the pin would stay on the syft it was cut with: the floating stable-1 tag it replaced moved to a fixed syft on its own, a digest pin does not. Tag and digest move together here, as the comment above the pin asks.",
echo "::error::This PR makes a sizeable API change (new group, new resource, or breaking change) and needs an approving review from one of: ${API_OWNERS}. See the job summary for details."
163
231
exit 1
232
+
233
+
# A dismissal or a request for changes can turn a green head red, and until
234
+
# the evaluation reports, about a minute later, the old `success` would still
235
+
# let the PR merge. Same opener as the "E2E Tests" lane. Pushes need none: a
236
+
# new head SHA starts with no status. Losing it to a transient API error only
237
+
# reopens that window, so it must not fail the run.
238
+
api-gate-pending:
239
+
name: Mark API review gate as re-evaluating
240
+
if: >-
241
+
${{ github.event_name == 'pull_request_review'
242
+
&& github.event.review.state != 'commented'
243
+
&& !github.event.pull_request.head.repo.fork }}
244
+
runs-on: ubuntu-latest
245
+
continue-on-error: true
246
+
permissions:
247
+
statuses: write
248
+
steps:
249
+
- name: Report pending "API Review Gate" commit status
Copy file name to clipboardExpand all lines: .github/workflows/cut-prerelease.yaml
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,7 @@ concurrency:
48
48
group: cut-prerelease
49
49
cancel-in-progress: false
50
50
51
-
# The tag write happens via the app token, not GITHUB_TOKEN, so the job needs
52
-
# only read scope on the default token.
51
+
# Tag and branch writes use the app token so their push events trigger CI.
53
52
permissions:
54
53
contents: read
55
54
@@ -58,6 +57,9 @@ jobs:
58
57
name: Cut ${{ inputs.tag }}
59
58
runs-on: ubuntu-latest
60
59
timeout-minutes: 10
60
+
permissions:
61
+
contents: read
62
+
actions: write
61
63
62
64
steps:
63
65
# Pure-input validation first — no token minted, no checkout, so a bad tag
@@ -345,13 +347,14 @@ jobs:
345
347
- name: Build the frozen line's packages artifact
346
348
if: steps.freeze.outputs.created == 'true'
347
349
env:
348
-
GH_TOKEN: ${{ steps.app-token.outputs.token }}
350
+
# workflow_dispatch can trigger a run with GITHUB_TOKEN.
351
+
GH_TOKEN: ${{ github.token }}
349
352
BRANCH: release-${{ steps.parse.outputs.line }}
350
353
run: |
351
354
if gh workflow run build-release.yaml --ref "$BRANCH"; then
352
355
echo "Dispatched build-release.yaml for $BRANCH; it publishes cozystack-packages:$BRANCH."
353
356
else
354
-
echo "::warning::Could not dispatch build-release.yaml for $BRANCH (the CI app may lack 'actions: write')."
357
+
echo "::warning::Could not dispatch build-release.yaml for $BRANCH."
355
358
echo "::warning::Until it runs, cozystack-packages:$BRANCH does not exist, and PRs onto $BRANCH test the image refs committed in the tree rather than the line's own build."
356
359
echo "::warning::Start it by hand: gh workflow run build-release.yaml --ref $BRANCH"
0 commit comments