Bump actions/upload-artifact from 4.6.2 to 7.0.1#3
Merged
pengfei-threemoonslab merged 1 commit intoApr 25, 2026
Merged
Conversation
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.6.2 to 7.0.1. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@ea165f8...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
added
dependencies
pengfei-threemoonslab
approved these changes
Apr 25, 2026
dependabot
Bot
deleted the
dependabot/github_actions/actions/upload-artifact-7.0.1
branch
pengfei-threemoonslab
added a commit
that referenced
this pull request
May 16, 2026
P2 #1 — build_release_decision crashed on Finding(id=None) because ContributionRule.finding_id is required-as-string. Direct/internal callers (test fixtures, plugin checks emitting Findings before assign_finding_ids, explain-finding rebuilding from a stripped report) hit a Pydantic ValidationError. Fix the _rule helper to fall back through finding.fingerprint to finding.check_id, both of which are guaranteed-present strings on a valid Finding. Adds an explicit regression test exercising both the fingerprint and check_id fallbacks. P2 #2 — sample expected reports carried /private/tmp/shipgate_regen/ paths in generated_reports[] from the v0.17 regen. Restored to the original repo convention (relative paths like expected/report.md) by running scan from each sample dir with output_dir='expected'. P3 #3 — added release_decision.contribution_rules[] to the canonical agent surface: a one-line entry in docs/agent-contract-current.md "Read these first for release gating", a new entry in contract.MANUAL_REVIEW_SIGNALS so contract --json exposes it (with a comment explaining why reviewers triaging review_items want the audit row), and the regenerated llms-full.txt that aggregates the contract doc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
pengfei-threemoonslab
added a commit
that referenced
this pull request
May 16, 2026
* Add release_decision.contribution_rules[] audit (v0.17) Adds a deterministic per-finding audit of how each finding contributed to the release decision. Exactly one row per report.findings entry, including suppressed; the (rule, category) pair documents which branch of the gate fired. Bumps report_schema_version 0.16 -> 0.17. Documents the existing v0.8 classification as the new "Release decision truth table" in STABILITY.md (10 rows + prose explainers covering baseline asymmetry and exit-code-vs-decision split). No semantic change: decision, blockers[], review_items[], fail_policy.exit_code, and strict-mode exit are byte-identical to v0.16. The audit reflects existing behavior, it does not modify it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Address PR review: id-less Finding crash, sample paths, contract surface P2 #1 — build_release_decision crashed on Finding(id=None) because ContributionRule.finding_id is required-as-string. Direct/internal callers (test fixtures, plugin checks emitting Findings before assign_finding_ids, explain-finding rebuilding from a stripped report) hit a Pydantic ValidationError. Fix the _rule helper to fall back through finding.fingerprint to finding.check_id, both of which are guaranteed-present strings on a valid Finding. Adds an explicit regression test exercising both the fingerprint and check_id fallbacks. P2 #2 — sample expected reports carried /private/tmp/shipgate_regen/ paths in generated_reports[] from the v0.17 regen. Restored to the original repo convention (relative paths like expected/report.md) by running scan from each sample dir with output_dir='expected'. P3 #3 — added release_decision.contribution_rules[] to the canonical agent surface: a one-line entry in docs/agent-contract-current.md "Read these first for release gating", a new entry in contract.MANUAL_REVIEW_SIGNALS so contract --json exposes it (with a comment explaining why reviewers triaging review_items want the audit row), and the regenerated llms-full.txt that aggregates the contract doc.
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
1 participant
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.2 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 READMEDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)