Repository navigation
chore(ci)(deps): bump actions/download-artifact from 4 to 8 - #1425
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[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 to 8. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@v4...v8) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: '8' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
added
the
dependencies
Contributor
|
PR author is not in the allowed authors list. |
Contributor
✅ Tests passed — 1414/1418
|
Contributor
|
Closing per the new Dependabot config in #1461: routine major version bumps are now off the schedule. If a CVE surfaces on this package, Dependabot will still reopen it as a security update — ignore rules do not apply to security updates. |
Dani Akash (DaniAkash)
deleted the
dependabot/github_actions/actions/download-artifact-8
branch
June 30, 2026 08:16
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. |
Dmitrii Vasilev (gHashTag)
added a commit
to gHashTag/BrowserOS
that referenced
this pull request
Sep 4, 2026
Filing N tasks does not give you N workers, and last round proved it on my own work: of four issues filed, browseros-ai#1420 and browseros-ai#1421 both named queen-tick.ts in their Boundary. Two bees may not write one file, so the scheduler correctly refused one with fileConflict and the fourth worker slot stayed empty while the backlog looked healthy. The conflict is a property of the WORK, so it is settled where the work is created. That is what Dependabot's grouping, Nx's file-keyed task graph and Kubernetes anti-affinity all do: tell the scheduler only about things that can coexist. author.mjs took candidates in the order they were measured and never asked. It now takes a disjoint batch, widest boundary first, excluding anything that collides with paths live dispatches already hold, and it PRINTS every candidate it set aside with the reason - a selector that drops work silently is indistinguishable from a broken one. disjoint.mjs compares paths component-wise, never as strings. rings/SR-0 is a string prefix of rings/SR-00/Queen.swift and is not a directory containing it; comparing raw prefixes is a recorded defect of this project. Run against the live board it immediately found a real double claim: rings/SR-02/ChatViewModel.swift is held by BOTH browseros-ai#1133 and browseros-ai#1240. A THIRD DETECTOR, because two were not enough variety to feed four workers. The backlog starved with the swarm at zero bees: author.mjs found fourteen real deficits and could file against NONE, every one already having an issue - one of the ones parked at the retry ceiling. L3 is repository law and is broken in 86 server files by 2690 characters, almost all box drawing in comment rules. That is the right kind of fuel: measurable by one grep, one file per task so N tasks really do give N workers, and renewable. Files with non-ASCII in live code are skipped, because rewriting a user-facing string is a change of behaviour. AND A FALSE REFUSAL OF MY OWN, caught by filing them. brief-gate demanded a promised identifier as the ONLY mechanically checkable criterion, so it refused three real cleanups - a cleanup defines nothing new. A command over a path the Boundary reserves, with an exact expected output, is a property of the TREE rather than of the report, and is harder to fake than an identifier. Accepted now, with the demand kept strict: exact output, and the path must be one the Boundary actually holds. Three negatives pin it. fp-check no longer counts NEVER ACTED as a false accusation. That state is a true statement about the world and the single most valuable line coverage.mjs prints - it is how the reaper's untested branch was found. Counting it here made every newly written tool look like a false accusation until its first act, which would have taught me to ignore the checker. The selftest fixture now mints its identifier per run. It used a fixed name, and once the file was committed that name existed in the tree five times - so brief-gate did exactly its job and refused the draft. The fixture had falsified its own premise by being saved. selftest 57/57. fp-check 19 known-good inputs, 0 accused. Three issues filed with pairwise disjoint boundaries: browseros-ai#1424, browseros-ai#1425, browseros-ai#1426. Co-authored-by: Dmitrii Vasilev <trackgmedernj@hotmail.com>
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 to 8.
Release notes
Sourced from actions/download-artifact's releases.
... (truncated)
Commits
3e5f45bAdd regression tests for CJK characters (#471)e6d03f6Add a regression test for artifact name + content-type mismatches (#472)70fc10cMerge pull request #461 from actions/danwkennedy/digest-mismatch-behaviorf258da9Add change docsccc058eFix linting issuesbd7976bAdd a setting to specify what to do on hash mismatch and default it toerrorac21fcfMerge pull request #460 from actions/danwkennedy/download-no-unzip15999bfAdd note about package bumps974686eBump the version tov8and add release notesfbe48b1Update test names to make it clearer what they doDependabot 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)