Skip to content

Bump actions/attest-build-provenance from 3.0.0 to 4.2.2 - #8

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/actions/attest-build-provenance-4.2.2
Closed

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/actions/attest-build-provenance-4.2.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 29, 2026

Copy link
Copy Markdown

Bumps actions/attest-build-provenance from 3.0.0 to 4.2.2.

Release notes

Sourced from actions/attest-build-provenance's releases.

v4.2.2

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.1.1...v4.2.2

v4.1.1

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.1.0...v4.1.1

v4.1.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.0.0...v4.1.0

v4.0.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 29, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/attest-build-provenance-4.2.2 branch from f0900bd to 8f14afb Compare September 3, 2026 17:07
Bumps [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) from 3.0.0 to 4.2.2.
- [Release notes](https://github.com/actions/attest-build-provenance/releases)
- [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md)
- [Commits](actions/attest-build-provenance@977bb37...4d10147)

---
updated-dependencies:
- dependency-name: actions/attest-build-provenance
  dependency-version: 4.2.2
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/attest-build-provenance-4.2.2 branch from 8f14afb to 2e20a3a Compare September 4, 2026 15:13
@dependabot @github

dependabot Bot commented on behalf of github Sep 4, 2026

Copy link
Copy Markdown
Author

Superseded by #15.

@dependabot dependabot Bot closed this Sep 4, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/attest-build-provenance-4.2.2 branch September 4, 2026 15:56
karthik1729 added a commit that referenced this pull request Sep 12, 2026
…olved, and a failed patch puts back what it wrote

Review findings #8, #9, #10, #43–#51, #93.

- `exec`'s job half read both streams with `read_to_end`: a command that
  printed without bound was the pod's memory. Both go through the same 4 MiB
  `Ring` a detached process uses, and `truncated` is what the ring dropped.
- `/fs/stat` read a whole file to sniff 8 KiB of it, and `grep` read every
  entry before deciding it was too large; both are bounded now.
- `confine` answers the RESOLVED path, so what was checked is what the caller
  opens — a symlink swapped after the check cannot redirect a write.
- A non-string argv entry was dropped silently, which shifted every argument
  after it; one helper in `tools/mod.rs` refuses it for `exec` and `watch`.
- `/fs/changes` walked git status twice for one answer; `numstat` takes the
  caller's changes.
- `Registry` rebuilt every set's schemas on every call to find one name; the
  index is built once.
- `patch` restores the files it already wrote when a later write or delete
  fails, as `edit` does, and the temp name carries the pid and a counter.
- `process_write` holds stdin behind an async mutex: a concurrent second write
  waits instead of being told the process takes no more input.
- Graft: a timed-out call drops its pending entry, the tree watcher uses
  `is_ignored_dir`, `which` checks the executable bit, the child's `tools/list`
  is compared once against the copied schema table, and the dead lines go.
- An explicit body limit on the router: axum's 2 MiB default refused a write
  the file tools themselves accept.
karthik1729 added a commit that referenced this pull request Sep 12, 2026
Review findings #3, #4, #5, #6, #7, #8, #9, #12, #15, #18, #19, #20, #82.

No listing here had a ceiling. `_catalog` stat-ed every unmarked image an
owner had to answer a page of two; `referrers` read every signature of a
subject on every pull of it; `api_refs`, `volumes`, `volumehistory` and
`index::list` each answered whatever was there. Each now takes `?n=`,
pages with the object store's own start-after where it has one, and says
so with a `Link`. `api_files` reads a size only when asked for one, and
`check_repo` scans as far as it can act and no further.

The ownership map's own bounds: a map write times out inside the lease
that authorised it rather than at it, the epoch is re-checked after every
bounded write, a prune pass gets one lease TTL as a whole instead of one
per entry, `all()` scans without the role lock held, and a clock reading
before a compiled-in floor decides nothing at all — it would have read
every live lease as expired and granted every repo away from its owner.

Also: the three image write routes get a body limit, and a by-tag push
hashes sha512 only for an image that actually holds a sha512 manifest.
`deepen-not` lists the repo's refs once and resolves a shorthand under
git's own prefixes, not by whichever ref happens to end in that name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants