mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-09-07 08:26:11 +00:00
* ci(security): add CodeQL SAST workflow for JS/TS and Python
CodeQL analyzes both languages on PR, main push, and weekly schedule.
Findings upload to the Security tab as SARIF. Advisory only on
introduction; promote to required check after baseline triage.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U1)
* ci(security): add Dependency Review PR gate
Blocks PRs introducing high+ severity dependency vulnerabilities.
Posts inline summary comment on failure. Required-check candidate
after one week of clean runs.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U2)
* ci(security): add Gitleaks secret scanning
PR runs scan the diff; main pushes scan full history.
Defense-in-depth on top of GitHub native push protection
(documented as a recommended Settings toggle in SECURITY.md).
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U3)
* ci(security): add OpenSSF Scorecard workflow
Weekly + on main push. SARIF uploads to Security tab; public
badge URL resolves after first scheduled run lands.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U4)
* ci(security): add zizmor workflow lint
Lints .github/workflows/** for known Actions security misconfigurations
(unpinned actions, dangerous interpolation, missing permissions).
Triggered only on PRs touching .github/**.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U5)
* ci(security): add Trivy container image scanning
Builds Dockerfile.cli and Dockerfile.web, then scans images for
HIGH/CRITICAL CVEs. Findings record-only on Security tab; not
PR-blocking. Weekly schedule + main push for freshness.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U6)
* docs(security): add SECURITY.md policy and Scorecard badge
Vulnerability disclosure policy points to GitHub Private Vulnerability
Reporting. Documents in-CI scans landed in this branch and recommended
admin actions for forks.
Plan: docs/plans/2026-05-03-001-feat-automated-security-scans-plan.md (U7)
* fix(review): apply autofix feedback
- CodeQL paths-ignore: replace brace expansion (parser.{c,js}) with two
explicit entries — CodeQL uses .gitignore-style globs that do NOT support
brace expansion, so the original pattern matched no files.
- Trivy: pin aquasecurity/trivy-action from @master to @0.28.0 — mutable
refs are a supply-chain risk and are exactly what zizmor (added in this
same plan) is meant to flag.
ce-code-review run: /tmp/compound-engineering/ce-code-review/20260503-104259-279c3bc4/
* docs(review): record residual review findings
ce-code-review autofix run flagged three downstream-resolver items
that are not blockers but should land before promoting any of the new
security workflows to required PR checks.
Source: /tmp/compound-engineering/ce-code-review/20260503-104259-279c3bc4/
* fix(ci-security): address all zizmor + dependency-review violations
Resolves all GitHub Advanced Security findings on PR #1297:
- Add 'persist-credentials: false' to actions/checkout in 5 workflows
(codeql, dependency-review, gitleaks, trivy, workflow-lint). Prevents
the GITHUB_TOKEN from persisting in .git/config for downstream steps
to read. Scorecard already had it.
- Pin every net-new third-party Action to a commit SHA (was: major-tag
refs flagged by zizmor as 'unpinned action reference'):
github/codeql-action -> v3.35.3 (0daab03)
actions/dependency-review-action -> v4.9.0 (2031cfc)
gitleaks/gitleaks-action -> v2.3.9 (ff98106)
ossf/scorecard-action -> v2.4.3 (4eaacf0)
docker/build-push-action -> v6.19.2 (10e90e3)
- Bump aquasecurity/trivy-action 0.28.0 -> 0.36.0 (ed142fd). Versions
< 0.35.0 are flagged by GHSA-69fq-xp46-6x23 (briefly compromised
supply chain). Caught by Dependency Review on the introducing PR.
- Pin pipx-installed zizmor to 1.24.1 (was unpinned 'pipx install
zizmor' resolving to latest at run time).
Removes the now-stale residual-findings doc since every item it
recorded is resolved on this branch.
* fix(ci-security): clear remaining zizmor findings
After landing the new security workflows, zizmor reported 5 high+
findings against pre-existing workflows (none introduced by this PR's
new files, all introduced by zizmor's wider scope). Resolved per
research at docs.zizmor.sh and PyO3/maturin issue #2425:
Real fixes (cache-poisoning):
- publish.yml + release-candidate.yml: add 'package-manager-cache:
false' to actions/setup-node. setup-node v5+ enables caching by
default when a packageManager field is present in package.json;
explicit opt-out keeps release installs hermetic and clears the
audit. Cost: ~30s slower per release run.
Documented exemptions (dangerous-triggers, .github/zizmor.yml):
- ci-report.yml: workflow_run is REQUIRED to post sticky comments
on fork PRs (forks have read-only GITHUB_TOKEN on pull_request).
- claude.yml: pull_request_target is required by claude-code-action
to access secrets and post fork-PR review comments. PR checkouts
pin fork HEAD SHA to mitigate TOCTOU.
- pr-labeler.yml: pull_request_target on the autolabel job needs
pull-requests:write. release-drafter runs with dry-run:true and
reads config from the BASE ref only.
Each exemption carries the documented mitigation in zizmor.yml.
workflow-lint.yml now passes --config to both the SARIF and the
gate invocations.
Local 'zizmor --config .github/zizmor.yml --min-severity high .'
reports: No findings to report. Good job!
395 lines
16 KiB
YAML
395 lines
16 KiB
YAML
name: Release Candidate
|
|
|
|
on:
|
|
# Publish a release-candidate build whenever a merge/commit lands on main.
|
|
# Docs/README-only changes are filtered out so prose updates don't
|
|
# cut a release.
|
|
push:
|
|
branches: [main]
|
|
paths-ignore:
|
|
- '**.md'
|
|
- 'docs/**'
|
|
- 'LICENSE'
|
|
workflow_dispatch:
|
|
inputs:
|
|
bump:
|
|
description: >-
|
|
Cycle policy. 'auto' (default) continues the active rc cycle on
|
|
this branch if there is one, otherwise bumps patch from latest.
|
|
Choose 'patch' / 'minor' / 'major' to explicitly start or reset
|
|
an rc cycle.
|
|
required: false
|
|
default: 'auto'
|
|
type: choice
|
|
options:
|
|
- auto
|
|
- patch
|
|
- minor
|
|
- major
|
|
force:
|
|
description: 'Publish even when HEAD already has an rc marker'
|
|
required: false
|
|
default: 'false'
|
|
type: choice
|
|
options:
|
|
- 'false'
|
|
- 'true'
|
|
|
|
# No workflow-level permissions — scoped per job below.
|
|
permissions: {}
|
|
|
|
# Concurrency convention: see CONTRIBUTING.md → "GitHub Actions — Concurrency Convention".
|
|
# Serialize all runs on the same ref (push + workflow_dispatch) to prevent two publishes
|
|
# racing on the rc counter. cancel-in-progress: false — the earlier merge publishes first.
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.ref }}
|
|
cancel-in-progress: false
|
|
|
|
jobs:
|
|
# ── Skip when HEAD already has an rc marker (retry / duplicate dispatch) ──
|
|
# The marker is a lightweight tag `rc/<HEAD_SHA>` pushed *before* `npm
|
|
# publish`, so a failed publish leaves the marker in place and the guard
|
|
# refuses to re-publish. Recovery path after a partial failure:
|
|
# git push --delete origin rc/<HEAD_SHA> v<RC_VERSION>
|
|
# then redispatch with force=true.
|
|
guard:
|
|
name: Check if release candidate should run
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 5
|
|
permissions:
|
|
contents: read
|
|
outputs:
|
|
should_run: ${{ steps.decide.outputs.should_run }}
|
|
head_sha: ${{ steps.decide.outputs.head_sha }}
|
|
steps:
|
|
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
|
|
with:
|
|
fetch-depth: 0
|
|
fetch-tags: true
|
|
|
|
- name: Decide
|
|
id: decide
|
|
shell: bash
|
|
env:
|
|
FORCE: ${{ inputs.force }}
|
|
BUMP_INPUT: ${{ inputs.bump }}
|
|
EVENT_NAME: ${{ github.event_name }}
|
|
run: |
|
|
set -euo pipefail
|
|
HEAD_SHA=$(git rev-parse HEAD)
|
|
echo "head_sha=$HEAD_SHA" >> "$GITHUB_OUTPUT"
|
|
|
|
if [ "$FORCE" = "true" ]; then
|
|
echo "Force flag set — running regardless of marker tag."
|
|
echo "should_run=true" >> "$GITHUB_OUTPUT"
|
|
exit 0
|
|
fi
|
|
|
|
# An explicit cycle reset on dispatch (bump != auto) also bypasses
|
|
# the dedup guard — the maintainer is deliberately asking for a
|
|
# new rc from the same commit.
|
|
if [ "$EVENT_NAME" = "workflow_dispatch" ] \
|
|
&& [ -n "${BUMP_INPUT:-}" ] \
|
|
&& [ "${BUMP_INPUT:-auto}" != "auto" ]; then
|
|
echo "Explicit bump=$BUMP_INPUT — bypassing marker dedup."
|
|
echo "should_run=true" >> "$GITHUB_OUTPUT"
|
|
exit 0
|
|
fi
|
|
|
|
# Dedup: is there already an rc/<HEAD_SHA> marker pointing at HEAD?
|
|
MARKER="rc/${HEAD_SHA}"
|
|
if git rev-parse "refs/tags/$MARKER" >/dev/null 2>&1; then
|
|
echo "HEAD already has marker $MARKER — skipping."
|
|
echo "should_run=false" >> "$GITHUB_OUTPUT"
|
|
else
|
|
echo "No marker on HEAD — proceeding."
|
|
echo "should_run=true" >> "$GITHUB_OUTPUT"
|
|
fi
|
|
|
|
# ── Reuse the stable CI workflow ─────────────────────────────────────
|
|
ci:
|
|
needs: guard
|
|
if: needs.guard.outputs.should_run == 'true'
|
|
uses: ./.github/workflows/ci.yml
|
|
permissions:
|
|
contents: read
|
|
secrets: inherit
|
|
|
|
# ── Publish the rc build to npm + create GitHub prerelease ───────────
|
|
publish:
|
|
name: Publish release candidate to npm
|
|
needs: [guard, ci]
|
|
if: needs.guard.outputs.should_run == 'true'
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 20
|
|
permissions:
|
|
contents: write # push rc tag + marker
|
|
id-token: write # npm provenance
|
|
outputs:
|
|
vtag: ${{ steps.reltag.outputs.vtag }}
|
|
steps:
|
|
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
|
|
with:
|
|
fetch-depth: 0
|
|
fetch-tags: true
|
|
|
|
- uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
|
|
with:
|
|
node-version: 20
|
|
registry-url: https://registry.npmjs.org
|
|
# Hermetic install — release-candidate produces shipped artifacts.
|
|
# setup-node v5+ caches by default when a packageManager field is
|
|
# present in package.json; explicit opt-out is required to clear
|
|
# the zizmor cache-poisoning audit. See cache-poisoning audit.
|
|
package-manager-cache: false
|
|
|
|
- name: Build gitnexus-shared
|
|
run: npm install && npm run build
|
|
working-directory: gitnexus-shared
|
|
|
|
- name: Install gitnexus dependencies
|
|
run: npm ci
|
|
working-directory: gitnexus
|
|
|
|
- name: Resolve rc version
|
|
id: version
|
|
shell: bash
|
|
working-directory: gitnexus
|
|
env:
|
|
BUMP_INPUT: ${{ inputs.bump }}
|
|
EVENT_NAME: ${{ github.event_name }}
|
|
PKG_NAME: gitnexus
|
|
run: |
|
|
set -euo pipefail
|
|
|
|
# 1. Current published `latest` — the floor for any new rc base.
|
|
# Only E404 ("never published") falls back to package.json; any
|
|
# other error (network, auth, malformed response) fails fast.
|
|
NPM_STDERR_LATEST="$(mktemp)"
|
|
if CURRENT_LATEST="$(npm view "$PKG_NAME" version 2>"$NPM_STDERR_LATEST")"; then
|
|
:
|
|
else
|
|
if grep -q 'E404' "$NPM_STDERR_LATEST"; then
|
|
CURRENT_LATEST="$(node -p "require('./package.json').version")"
|
|
echo "Package not on registry (E404) — seeding from package.json: $CURRENT_LATEST"
|
|
else
|
|
echo "::error::npm registry unreachable for 'view version':" >&2
|
|
cat "$NPM_STDERR_LATEST" >&2
|
|
rm -f "$NPM_STDERR_LATEST"
|
|
exit 1
|
|
fi
|
|
fi
|
|
rm -f "$NPM_STDERR_LATEST"
|
|
CURRENT_LATEST_CLEAN="${CURRENT_LATEST%%-*}"
|
|
|
|
# 2. Full version list — needed for the counter and for active-cycle
|
|
# inference. Same E404-only fallback.
|
|
NPM_STDERR_VERSIONS="$(mktemp)"
|
|
if VERSIONS_JSON="$(npm view "$PKG_NAME" versions --json 2>"$NPM_STDERR_VERSIONS")"; then
|
|
:
|
|
else
|
|
if grep -q 'E404' "$NPM_STDERR_VERSIONS"; then
|
|
VERSIONS_JSON='[]'
|
|
echo "No published versions for $PKG_NAME yet (E404)."
|
|
else
|
|
echo "::error::npm registry unreachable for 'view versions':" >&2
|
|
cat "$NPM_STDERR_VERSIONS" >&2
|
|
rm -f "$NPM_STDERR_VERSIONS"
|
|
exit 1
|
|
fi
|
|
fi
|
|
rm -f "$NPM_STDERR_VERSIONS"
|
|
|
|
# 3. Base selection.
|
|
# - workflow_dispatch + bump ∈ {patch,minor,major} → explicit cycle
|
|
# reset from latest.
|
|
# - Everything else (push, or dispatch with bump=auto) → continue
|
|
# the highest active rc base > latest if one exists; else
|
|
# default to patch from latest.
|
|
if [ "$EVENT_NAME" = "workflow_dispatch" ] \
|
|
&& [ -n "${BUMP_INPUT:-}" ] \
|
|
&& [ "${BUMP_INPUT:-auto}" != "auto" ]; then
|
|
BASE="$(npx --yes -p semver@7 semver -i "$BUMP_INPUT" "$CURRENT_LATEST_CLEAN")"
|
|
echo "Explicit bump=$BUMP_INPUT → BASE=$BASE"
|
|
else
|
|
cat > /tmp/active_base.mjs <<'NODESCRIPT'
|
|
const latest = process.env.LATEST;
|
|
let v;
|
|
try { v = JSON.parse(process.env.VERSIONS_JSON); } catch { v = []; }
|
|
if (!Array.isArray(v)) v = [v];
|
|
const parse = s => s.split(".").map(n => parseInt(n, 10));
|
|
const gt = (a, b) => {
|
|
const [A, B] = [parse(a), parse(b)];
|
|
for (let i = 0; i < 3; i++) if (A[i] !== B[i]) return A[i] > B[i];
|
|
return false;
|
|
};
|
|
const bases = new Set();
|
|
for (const s of v) {
|
|
const m = /^(\d+\.\d+\.\d+)-rc\.\d+$/.exec(s);
|
|
if (m && gt(m[1], latest)) bases.add(m[1]);
|
|
}
|
|
if (!bases.size) { process.stdout.write(""); process.exit(0); }
|
|
const sorted = [...bases].sort((a, b) => gt(a, b) ? 1 : -1);
|
|
process.stdout.write(sorted[sorted.length - 1]);
|
|
NODESCRIPT
|
|
ACTIVE_BASE="$(LATEST="$CURRENT_LATEST_CLEAN" VERSIONS_JSON="$VERSIONS_JSON" node /tmp/active_base.mjs)"
|
|
if [ -n "$ACTIVE_BASE" ]; then
|
|
BASE="$ACTIVE_BASE"
|
|
echo "Continuing active rc cycle → BASE=$BASE"
|
|
else
|
|
BASE="$(npx --yes -p semver@7 semver -i patch "$CURRENT_LATEST_CLEAN")"
|
|
echo "No active rc cycle → patch bump from latest → BASE=$BASE"
|
|
fi
|
|
fi
|
|
|
|
# 4. Counter: 1 + max existing N for `${BASE}-rc.*`, else 1.
|
|
cat > /tmp/next_rc.mjs <<'NODESCRIPT'
|
|
const base = process.env.BASE;
|
|
const prefix = base + "-rc.";
|
|
let v;
|
|
try { v = JSON.parse(process.env.VERSIONS_JSON); } catch { v = []; }
|
|
if (!Array.isArray(v)) v = [v];
|
|
const ns = v
|
|
.filter(s => typeof s === "string" && s.startsWith(prefix))
|
|
.map(s => parseInt(s.slice(prefix.length), 10))
|
|
.filter(n => Number.isInteger(n) && n >= 0);
|
|
process.stdout.write(String(ns.length ? Math.max(...ns) + 1 : 1));
|
|
NODESCRIPT
|
|
NEXT_N="$(BASE="$BASE" VERSIONS_JSON="$VERSIONS_JSON" node /tmp/next_rc.mjs)"
|
|
RC_VERSION="${BASE}-rc.${NEXT_N}"
|
|
echo "Computed rc: $RC_VERSION"
|
|
|
|
# 5. Defensive: if the exact version already exists on the registry
|
|
# (e.g., race with another run), abort before re-publishing.
|
|
# Same E404-only pattern used above — a transient network
|
|
# failure must fail loudly, not pretend the version is missing.
|
|
NPM_STDERR_EXISTS="$(mktemp)"
|
|
if npm view "$PKG_NAME@$RC_VERSION" version 2>"$NPM_STDERR_EXISTS" >/dev/null; then
|
|
rm -f "$NPM_STDERR_EXISTS"
|
|
echo "::error::Version $RC_VERSION already exists on npm — aborting."
|
|
exit 1
|
|
else
|
|
if grep -qiE 'E404|not found' "$NPM_STDERR_EXISTS"; then
|
|
rm -f "$NPM_STDERR_EXISTS"
|
|
# Version doesn't exist — safe to proceed.
|
|
else
|
|
echo "::error::npm registry unreachable for existence check:" >&2
|
|
cat "$NPM_STDERR_EXISTS" >&2
|
|
rm -f "$NPM_STDERR_EXISTS"
|
|
exit 1
|
|
fi
|
|
fi
|
|
|
|
echo "base=$BASE" >> "$GITHUB_OUTPUT"
|
|
echo "rc_n=$NEXT_N" >> "$GITHUB_OUTPUT"
|
|
echo "rc_version=$RC_VERSION" >> "$GITHUB_OUTPUT"
|
|
|
|
- name: Apply rc version in-CI
|
|
shell: bash
|
|
working-directory: gitnexus
|
|
run: |
|
|
set -euo pipefail
|
|
npm version "${{ steps.version.outputs.rc_version }}" \
|
|
--no-git-tag-version --allow-same-version
|
|
|
|
- name: Build gitnexus
|
|
run: npm run build
|
|
working-directory: gitnexus
|
|
|
|
- name: Dry-run publish
|
|
run: npm publish --dry-run --tag rc
|
|
working-directory: gitnexus
|
|
|
|
# ── Acquire the "rc lock" BEFORE publishing (fixes idempotency) ─────
|
|
# We create two tags and push them atomically:
|
|
# v<RC_VERSION> → annotated tag on a detached release commit
|
|
# whose tree contains the rewritten package.json
|
|
# (so the tag's source matches the npm tarball)
|
|
# rc/<HEAD_SHA> → lightweight tag on HEAD; the guard's dedup key
|
|
# If this push fails, nothing is published — safe.
|
|
# If this push succeeds but npm publish fails, the marker stays on
|
|
# the remote and blocks retries until an operator manually cleans up.
|
|
- name: Create and push rc tags
|
|
id: reltag
|
|
shell: bash
|
|
working-directory: gitnexus
|
|
env:
|
|
RC_VERSION: ${{ steps.version.outputs.rc_version }}
|
|
HEAD_SHA: ${{ needs.guard.outputs.head_sha }}
|
|
run: |
|
|
set -euo pipefail
|
|
VTAG="v${RC_VERSION}"
|
|
MARKER="rc/${HEAD_SHA}"
|
|
git config user.name 'github-actions[bot]'
|
|
git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
|
|
|
|
# Detached release commit with the version bump — keeps `main`
|
|
# pristine but gives the v-tag a tree that matches the published
|
|
# package contents exactly (fixes release-integrity gap).
|
|
git add package.json package-lock.json 2>/dev/null || git add package.json
|
|
git commit -m "release: ${VTAG}" --allow-empty
|
|
RELEASE_SHA="$(git rev-parse HEAD)"
|
|
echo "Detached release commit: $RELEASE_SHA"
|
|
|
|
# Annotated release tag on the release commit.
|
|
git tag -a "$VTAG" "$RELEASE_SHA" -m "$VTAG"
|
|
# Lightweight marker on the user-visible HEAD for the guard.
|
|
git tag "$MARKER" "$HEAD_SHA"
|
|
|
|
# Atomic push of both refs. If either would clobber an existing
|
|
# remote ref, the push fails and we stop before npm publish.
|
|
git push --atomic origin "refs/tags/$VTAG" "refs/tags/$MARKER"
|
|
|
|
echo "vtag=$VTAG" >> "$GITHUB_OUTPUT"
|
|
echo "marker=$MARKER" >> "$GITHUB_OUTPUT"
|
|
echo "release_sha=$RELEASE_SHA" >> "$GITHUB_OUTPUT"
|
|
|
|
- name: Publish to npm (rc dist-tag)
|
|
run: npm publish --provenance --access public --tag rc
|
|
working-directory: gitnexus
|
|
env:
|
|
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
|
|
- name: Create GitHub prerelease
|
|
uses: softprops/action-gh-release@b4309332981a82ec1c5618f44dd2e27cc8bfbfda # v2
|
|
with:
|
|
tag_name: ${{ steps.reltag.outputs.vtag }}
|
|
name: Release Candidate ${{ steps.reltag.outputs.vtag }}
|
|
prerelease: true
|
|
make_latest: 'false'
|
|
generate_release_notes: true
|
|
body: |
|
|
Automated release candidate build from `main`.
|
|
|
|
**npm:** `npm install gitnexus@rc`
|
|
**Version:** `${{ steps.version.outputs.rc_version }}`
|
|
**Target base:** `${{ steps.version.outputs.base }}` (rc #${{ steps.version.outputs.rc_n }})
|
|
**Source commit (main):** ${{ needs.guard.outputs.head_sha }}
|
|
**Release commit (versioned tree):** ${{ steps.reltag.outputs.release_sha }}
|
|
|
|
Release candidates are pre-stable builds intended for early testing.
|
|
Stable releases remain on the `latest` dist-tag.
|
|
|
|
# ── Build & push RC Docker images ────────────────────────────────────
|
|
# Calls docker.yml as a reusable workflow so that the build, signing, and
|
|
# attestation logic stays in one place. The publish job exposes `vtag`
|
|
# (e.g. `v1.2.3-rc.1`) as an output so we can pass it as the tag input.
|
|
# RC images are signed with Cosign keyless signing; the OIDC identity
|
|
# will be `docker.yml@refs/heads/main` (the caller's ref) rather than a
|
|
# tag ref — see README.md § Docker for the correct verify command for RCs.
|
|
docker:
|
|
name: Build & Push RC Docker images
|
|
needs: [guard, publish]
|
|
if: needs.guard.outputs.should_run == 'true' && needs.publish.outputs.vtag != ''
|
|
uses: ./.github/workflows/docker.yml
|
|
# Reusable workflows do not receive caller secrets unless inherited; without
|
|
# this, DOCKERHUB_* / GITHUB_TOKEN are empty in docker.yml → "Username and
|
|
# password required" on Docker Hub login (see same pattern on `ci:` above).
|
|
secrets: inherit
|
|
permissions:
|
|
contents: read
|
|
packages: write
|
|
id-token: write
|
|
attestations: write
|
|
with:
|
|
tag: ${{ needs.publish.outputs.vtag }}
|