Repository navigation
ci: bump actions/upload-artifact from 4.6.0 to 7.0.1 - #4
Merged
leonacostaok merged 1 commit intoJul 15, 2026
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Member
|
@dependabot rebase |
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.6.0 to 7.0.1. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@65c4c4a...043fb46) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7.0.1
branch
from
July 15, 2026 18:57
ec0fe4c to
84e3af0
Compare
leonacostaok
deleted the
dependabot/github_actions/actions/upload-artifact-7.0.1
branch
July 15, 2026 19:06
Member
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR has already been merged! |
leonacostaok
added a commit
that referenced
this pull request
Jul 20, 2026
… + counts - ADR-0005 + THREAT-MODEL: F1 (blast-radius gate), F2 (system-role instruction/ data separation), F3 (--max-findings spend cap) are fixed in code — mark them resolved instead of open, consistent with ROADMAP §1 (verified in loop.ts, remediate-pipeline.ts, triage-run.ts). - COMPLIANCE: SP 800-208 now has the stateful-hbs detector (was 'no detector'); A.8.24 evidence chain is shipped (#4 done); CBOM described by assetType; OpenVEX export noted. - Version drift v0.4.2 -> v0.5.0 (tagged; 0.4.4 published) across COMPLIANCE, VERSIONING, AUDIT, SUPPLY-CHAIN; test-count and 'supported vs benchmark-corpus languages' wording refreshed; CHANGELOG Fixed section for the audit hardening.
leonacostaok
added a commit
that referenced
this pull request
Jul 29, 2026
* core+qscan: policy-as-code mandate compliance gate roadmap #4 (engine + CLI). adds a dated, clause-named compliance layer on top of the family-only CryptoPolicy: - core/mandates.ts: mandate catalog (CNSA 2.0, NIST IR 8547 with real 2030/2035 deadlines) + evaluateMandates (per-finding conformant/due/violation vs today, naming clause+deadline+citation) + mandateGateFails. pure, 10 tests. - qscan: --mandate <id> (repeatable), --lead-months, --fail-now. deadline-aware default: reports every prohibited finding with its clause+deadline, fails the build only once a deadline passes (or early via the flags). gate uses the same raw findings as the exit code, so triage can't flip it. compliance block in the human report. no detection change (bench agrees on 834 findings); no action change yet (no re-bundle). unpublished on main. * mandate gate: audit fixes + 0.7.0 audit remediation before release: - core/mandates: derive deadlines from PQC_STANDARDS.transitionTimeline (no hardcoded 2030/2035; drift test added), tier deprecate(warn)/disallow(fail) so both clauses are live and the default gate fails only at disallow, drop X25519/ X448 (hybrid leg false-positive), notInScope for out-of-scope findings, honest conformant count, assertKnownMandates (fail-loud in core), node:test rewrite - qscan: use assertKnownMandates; human block shows deprecated tier + notInScope - action: mandate/lead-months/fail-now inputs; fails naming clause+deadline+citation; mandate section in summary + PR comment; tests; dist re-bundled - docs: COMPARISON (family-level gate, parameter-level still future), COMPLIANCE §4, CHANGELOG (0.6.0 backfill + 0.7.0 Unreleased), README - api-surface regenerated; all packages 0.7.0 (minor, per VERSIONING.md) deferred to 0.7.x: machine-readable mandate output (sarif/json/evidence), compose with --policy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/upload-artifact from 4.6.0 to 7.0.1.
Release notes
Sourced from actions/upload-artifact's releases.
... (truncated)
Commits
043fb46Merge pull request #797 from actions/yacaovsnc/update-dependency634250cInclude changes in typespec/ts-http-runtime 0.3.5e454baaReadme: bump all the example versions to v7 (#796)74fad66Update the readme with direct upload details (#795)bbbca2dSupport direct file uploads (#764)589182cUpgrade the module to ESM and bump dependencies (#762)47309c9Merge pull request #754 from actions/Link-/add-proxy-integration-tests02a8460Add proxy integration testb7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in README