ci: Bump ossf/scorecard-action from 2.4.3 to 2.4.4 - #10
Merged
github-actions[bot] merged 1 commit intoJul 30, 2026
Merged
Conversation
Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.4.3 to 2.4.4. - [Release notes](https://github.com/ossf/scorecard-action/releases) - [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md) - [Commits](ossf/scorecard-action@4eaacf0...2d11466) --- updated-dependencies: - dependency-name: ossf/scorecard-action dependency-version: 2.4.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
deleted the
dependabot/github_actions/ossf/scorecard-action-2.4.4
branch
July 30, 2026 12:10
HetCreep
added a commit
that referenced
this pull request
Aug 8, 2026
…under an agent dir Per-project .coalface.json now lives under an agent dir, never bare at the project root. Owner-designated shape (2026-08-08), the read order is a RAIL identical across the whole series: 1. <project>/.<the running agent's own dir>/coal/coalface.json -- the dir of the agent ACTUALLY EXECUTING. CoalFace is the first room in this campaign wired to more than one agent (hooks/coalface-conductor.js for Claude Code, hooks/ag-conductor.js for Antigravity), so this is a real branch here, not a hypothetical: own dir is 'claude' from the CC hook's own main(), 'agents' from the AG adapter -- both pass it explicitly into the now-shared readCfg(ownAgentDir). 2. other known agent dirs, fixed order .claude -> .agents -> .gemini (first found wins; own dir deduped out so it's never checked twice) 3. LEGACY: <project>/.coalface.json at the project root (the pre-2026-08-08 shape) -- still read normally, no breakage findProjectCfg() keeps its existing per-level walk-up-from-cwd shape (stop at home, Phoenix #10/CoalBoard v1.5.1) and now checks the full candidate list AT EACH LEVEL before moving to the parent, so a new-shape config one level down still wins over a legacy config further up -- same nearest-wins behavior as before the migration. Write side: no project-config writer exists anywhere in this codebase (no configure.mjs, no consent-persistence code) -- confirmed by a grep-proof N/A test, not just asserted in prose. Scratch state (#39 half): the update-check stamp moves from ~/.claude/.coalface-update-check to ~/.claude/coal/coalface/update-check, read-new-fallback-old (a pre-migration stamp's throttle window still holds) / write-new-drop-old (every write lands only at the new path; an old-shape file found on a due check is removed in the same operation -- no-old-version-leftover, never on a read-only path per Phoenix #5/no-side-effects). The safer-value-wins clamp (hooks-safety.md #9) is untouched by design -- only the file's ADDRESS moved. Proven, not assumed: case 38 attempts an escalation through a NEW own-dir candidate path and confirms the clamp still holds the explicit global floor. Global config (~/.claude/.coalface.json) is UNCHANGED -- out of this room's #69+#39 scope per the design doc's own checklist item 3, which names only the update-check stamp; matches CoalBoard's precedent in the same campaign. +7 tests (32->39 in hooks.test.mjs, 50->57 overall): 3 read-order precedence (own-dir wins over the fixed order · fixed order used when own-dir absent · legacy fallback when no new-shape candidate exists anywhere), 2 stamp-migration (read-new-fallback-old · write-new-drop-old), 1 clamp-unchanged, 1 write-side grep-proof N/A. The own-dir-precedence and write-new-drop-old cases mutation-tested red-first against the exact behavior each claims (own-dir-first removed -> only case 33 fails; drop-old removed -> only case 37 fails) before being trusted. Docs (README/PRIVACY/SECURITY/SKILL.md/CONTRIBUTING) not yet updated -- separate DOCS station commit follows. No version bump here (dist DOES change, but SemVer sizing is the RELEASE station's job per this campaign's own checklist item 7 and CoalBoard's shipped precedent in the same batch). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.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
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 ossf/scorecard-action from 2.4.3 to 2.4.4.
Release notes
Sourced from ossf/scorecard-action's releases.
Commits
2d11466Bump action tag for v2.4.4 release (#1688)1bd3285🌱 Bump the docker-images group across 1 directory with 2 updates (#1...913edce🌱 Bump github.com/containerd/containerd from 1.7.32 to 1.7.33 (#1671)0957b8f🌱 Bump golang.org/x/net from 0.56.0 to 0.57.0 (#1680)f0061eb🌱 Bump google.golang.org/grpc from 1.81.1 to 1.82.1 (#1687)20ee732🌱 Bump github.com/sigstore/cosign/v2 from 2.6.3 to 2.6.4 (#1685)9f295ef🌱 Bump the github-actions group with 6 updates (#1686)69bf556🌱 Bump github.com/sigstore/sigstore-go from 1.1.4 to 1.2.0 (#1681)94e8b96🌱 Bump github.com/sigstore/rekor from 1.5.0 to 1.5.2 (#1673)c7a1b37🌱 Bump github.com/sigstore/fulcio from 1.8.5 to 1.8.6 (#1675)Dependabot 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)