build(deps): Bump actions/download-artifact from 4.3.0 to 7.0.0 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps): Bump actions/download-artifact from 4.3.0 to 7.0.0#2dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4.3.0 to 7.0.0. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@d3f86a1...37930b1) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
roborev: Combined Review (
|
3 tasks
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/download-artifact-7.0.0
branch
February 22, 2026 17:57
wesm
added a commit
to aaronflorey/agentsview
that referenced
this pull request
Jul 3, 2026
Devin transcript failures are meant to be safe to surface, but path-bearing os.PathError values can include the raw transcript path and session id when formatted directly. Sanitizing that cause keeps the underlying error available via Unwrap while avoiding accidental source-path disclosure. Malformed Devin rows can also omit both activity timestamps. Treating that freshness value as zero keeps one partial row from breaking discovery or parsing for the provider. VALID (fixed): kenn-io#1, kenn-io#2
wesm
added a commit
that referenced
this pull request
Jul 5, 2026
Embedding endpoint 4xx responses are not all document-specific. Treating route, schema, model, or media-type failures as permanent skip-stamped entire corpora and could activate an empty generation, leaving later incremental builds with nothing to retry. Keep embeddings routes registered even when vector serving is disabled so OpenAPI and generated clients expose the API surface, with handlers returning 501 until a manager is wired. Semantic and hybrid search now require an explicit intent header over GET so blind browser no-CORS requests cannot spend embeddings quota through the local daemon; daemon-backed clients set that header. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 6, 2026
Embedding endpoint 4xx responses are not all document-specific. Treating route, schema, model, or media-type failures as permanent skip-stamped entire corpora and could activate an empty generation, leaving later incremental builds with nothing to retry. Keep embeddings routes registered even when vector serving is disabled so OpenAPI and generated clients expose the API surface, with handlers returning 501 until a manager is wired. Semantic and hybrid search now require an explicit intent header over GET so blind browser no-CORS requests cannot spend embeddings quota through the local daemon; daemon-backed clients set that header. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
to rodboev/agentsview
that referenced
this pull request
Jul 7, 2026
VALID (fixed): kenn-io#1 -- HTTP remote sync could stream raw Windsurf workspace SQLite state and sidecars to any bearer-token holder allowed to request remote archives. VALID (fixed): kenn-io#2 -- Windsurf freshness and remote target selection treated transient SQLite SHM files as durable session inputs. Windsurf HTTP archives now synthesize a filtered state.vscdb containing only the chat keys the parser consumes, while preserving workspace metadata for project naming. SHM is no longer watched, fingerprinted, or resolved, and SSH tar input skips paths that disappear after resolution so optional WAL sidecars do not abort transfer.
wesm
added a commit
that referenced
this pull request
Jul 10, 2026
Text preselection could discard entries whose only score came from structured metadata or temporal intent, while versioned eval corpora could not be isolated through the supported query surface. Preserve those ranking candidates and expose the existing versioned source-session identity as corpus_id so harnesses can query one corpus without deleting history. VALID (fixed): #1 candidate selection, #2 eval corpus versioning.
wesm
added a commit
that referenced
this pull request
Jul 10, 2026
Eval corpus ingestion must remain idempotent under concurrent harness requests and must not expose partially indexed trajectories. Evidence imports must also preserve context budget when several tool uses support the same snippet. VALID (fixed): #1 eval ingestion atomicity, #2 duplicate evidence context.
wesm
added a commit
that referenced
this pull request
Jul 12, 2026
Scheduled and API-triggered HTTP syncs must use one lock order or overlapping work can deadlock the daemon. Failed archive extraction setup must also retain downloaded spools for cleanup retry, especially when disk or filesystem failures are already present. Multi-source rebuild safety now evaluates each source independently so successful work from one source cannot authorize swapping an incomplete archive for another, while contributor cancellation and failure diagnostics remain observable. VALID (fixed): #1 lock-order inversion, #2 extraction setup cleanup leak, #3 per-source rebuild safety INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 13, 2026
The project-evidence shape changed incompatibly after the original v1 surfaces shipped, but the public usage, activity, and session-summary payloads still reported version 1. Mark the current shape as v2 so consumers can reject the transitional 0.38.0/0.38.1 payloads safely. Screenshot extraction also retained source identity evidence outside sessions.machine. Remove those source rows and journals so generated docs assets cannot republish local machine or repository context. VALID (fixed): #1, #2
wesm
added a commit
that referenced
this pull request
Jul 14, 2026
Repair queue rows are durable, but cancellation after scanning could make status recounts share the canceled context and erase evidence of queued work. Use a bounded detached recount for all post-scan exits, retaining a committed-count fallback when recounting itself fails. Keep the fallback-path test on the vector package's selected SQLite driver so it exercises the same contract on cgo and modernc configurations. VALID (fixed): #1, #2
wesm
added a commit
that referenced
this pull request
Jul 14, 2026
Repair integrity scans must remain bounded by the scanned documents, even when one document has many chunks. Fetching content once per document avoids multiplying content transfer and allocation by chunk count while preserving the same validation contract. Embeddings commands also need to distinguish an incompatible live daemon from a genuinely unreachable one so users receive the existing restart guidance after an API upgrade. VALID (fixed): #1, #2 INVALID (dismissed): #3, #4 -- already fixed by 929db2d
wesm
added a commit
to mjacobs/agentsview
that referenced
this pull request
Jul 19, 2026
Palette-owned Escape handling must not reach the document shortcut after clearing the modal, because that reinterprets one keypress as a session deselection. Initial build-status probes also need to distinguish failure and successful completion from a never-built ready state so the panel does not hide errors or offer redundant work.\n\nVALID (fixed): #1, kenn-io#2
mjacobs
pushed a commit
to mjacobs/agentsview
that referenced
this pull request
Jul 19, 2026
Palette-owned Escape handling must not reach the document shortcut after clearing the modal, because that reinterprets one keypress as a session deselection. Initial build-status probes also need to distinguish failure and successful completion from a never-built ready state so the panel does not hide errors or offer redundant work.\n\nVALID (fixed): #1, kenn-io#2
wesm
added a commit
that referenced
this pull request
Jul 23, 2026
Complete container parses infer missing members from stored ownership; those absences must remain revivable archive tombstones rather than parser exclusions. Watcher retries also need an authoritative replay after a failed write advances the provider cursor. Split schemas now combine indexed single-workspace timestamps with a fixed recent-member window so metadata and usage commits converge without making routine event work scale with the conversation archive. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 23, 2026
An empty authoritative database is valid deletion proof, not a parser exclusion. Retaining its stored ownership as revivable tombstones prevents deletion of the final source conversation from erasing archived sessions and messages. Container scans can be archive-sized, so caller cancellation must reach the shared-container callback, database reads, and per-conversation loop boundaries. VALID (fixed): #1, #2 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 23, 2026
Workspace-qualified identities must retain user trash and permanent exclusion state instead of resurfacing deleted conversations. Explicit migration relationships let cleanup honor that state without rewriting archived primary keys. Omnigent watcher discovery is intentionally bounded, so scheduled streamed reconciliation remains the authoritative backstop for edits outside its cursors. Pending correctness retries also bypass incremental cutoffs and are acknowledged only after successful work. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 23, 2026
A failed member parse can advance one root's bounded cursor, so unrelated scoped work must not acknowledge the global replay generation. Only an unscoped pass provides the coverage needed to clear that recovery state. Remote copies of a live WAL database also need transactional snapshot semantics. Exporting one online-backup database avoids inconsistent main/WAL combinations and keeps unrelated Omnigent state out of HTTP and SSH archives. Recorded aggregate usage cost remains authoritative when Omnigent provides model token breakdowns without model costs. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
wesm
added a commit
that referenced
this pull request
Jul 23, 2026
Omnigent stores transcript data beside authentication credentials in the same SQLite database. A page-level backup cannot provide a safe remote artifact, so HTTP and SSH sync must exclude the provider until a fresh allowlisted export schema exists. This also makes snapshot-tool failures irrelevant instead of allowing successful empty imports. Persisted container cache hits still need to restore the bounded in-memory change cursors after process restart. Rebuilding only cursor tails, workspace bounds, and the fixed recent-member window preserves watcher cardinality without reparsing the archive; a fingerprint recheck closes the commit race during restoration. VALID (fixed): #1, #2, #3 INVALID (dismissed): none PEDANTIC (skipped): none
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/download-artifact from 4.3.0 to 7.0.0.
Release notes
Sourced from actions/download-artifact's releases.
... (truncated)
Commits
37930b1Merge pull request #452 from actions/download-artifact-v7-release72582b9doc: update readme0d2ec9dchore: release v7.0.0 for Node.js 24 supportfd7ae8fMerge pull request #451 from actions/fix-storage-blobd484700chore: restore minimatch.dep.yml license file03a8080chore: remove obsolete dependency license files56fe6d9chore: update@actions/artifactlicense file to 5.0.18e3ebc4chore: update package-lock.json with@actions/artifact@5.0.11e3c4b4fix: update@actions/artifactto ^5.0.0 for Node.js 24 punycode fix458627dchore: use local@actions/artifactpackage for Node.js 24 testingDependabot 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)