chore(deps): bump actions/checkout from 4.2.2 to 6.0.2#10
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump actions/checkout from 4.2.2 to 6.0.2#10dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
ciprianiacobescu
approved these changes
May 16, 2026
Contributor
ciprianiacobescu
left a comment
ciprianiacobescu
left a comment
There was a problem hiding this comment.
Bulk approval of Dependabot dependency update. Manual merge after CI workflow remediation completes.
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
e775658 to
74308da
Compare
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
74308da to
60da8b7
Compare
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
5 times, most recently
from
622f10c to
ea2f41a
Compare
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
2 times, most recently
from
d4bd77e to
be1f7be
Compare
ciprianiacobescu
pushed a commit
that referenced
this pull request
May 23, 2026
…lthchecks Round-trip validation v3 surfaced 2 more bugs after #4–#8 were fixed. Bug #9: dev-restore.sh processed manifest entries in order. The pg_dump iteration stopped services, applied the dump, restarted them. Then the volume iterations (vault_data, vault_kek, bootstrap_secrets) restored tarballs WHILE vault-adapter / proxy-plugin were already running with stale file handles into those volumes. Net effect: post-restore the volumes were correct on disk, but vault-adapter served "GetCredential not found" from the old inode → proxy → HTTP 502 "vault error". Fix: after the manifest loop completes (so ALL volumes + the pg_dump are restored), restart every data-dependent service ONCE. This drops all stale handles + in-memory caches regardless of manifest order. Bug #10: `docker compose restart` is fire-and-forget. It returns as soon as the docker daemon kicks the containers, NOT when they're actually responsive. End-to-end test showed admin-ui returning fast enough to confuse the verifier into "Connection reset by peer" while uvicorn was still bootstrapping in mcp-server / admin-api. Fix: chain `docker compose up -d --wait --timeout 180` after the restart. up -d is a no-op for already-running containers, but --wait blocks until every service's compose healthcheck passes (or times out). Callers can now hit /v1/tools/list_services immediately after the script returns and get a real response, not Connection-reset. Round-trip test v3 (with #7 #8 #9 #10): backup → docker compose down -v → up → dev-restore.sh → verify WITHOUT ANY manual SQL, manual GRANTs, manual restarts, or sleeps: [1/4] list_services HTTP 200 ✅ [2/4] request_token HTTP 200 ✅ [3/4] proxy → GitHub HTTP 200 ✅ authenticated as ciprianiacobescu [4/4] admin password yAPal2y2J... ✅ matches pre-backup Success criterion met: "after restore I do not need to change anything." Final tally of session-discovered backup/restore bugs (all fixed): #1 ✅ pg_dump silently skipped — Service field (51e7077) #2 ✅ vault-adapter detection — same class (a47a4e6) #3 ✅ host-file admin_password drift (49d519a) #3a ✅ Makefile colon-pattern blocked make admin-password (77ab040) #4 ✅ pg_dump --clean --if-exists (a1dc9e3) #5 ✅ psql errors surfaced (a1dc9e3) #6 ✅ restore stops dependent services (a1dc9e3) #7 ✅ pg_dump includes GRANTs (2fba9c3) #8 ✅ restore stops vault-adapter + proxy-plugin (2fba9c3) #9 ✅ this commit — post-loop service restart, manifest-order independent #10 ✅ this commit — restart waits for healthchecks
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.2 to 6.0.2. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@11bd719...de0fac2) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
be1f7be to
be735c4
Compare
Contributor
Author
|
Superseded by #120. |
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/checkout from 4.2.2 to 6.0.2.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...8e8c483Clarify v6 README (#2328)033fa0dAdd worktree support for persist-credentials includeIf (#2327)c2d88d3Update all references from v5 and v4 to v6 (#2314)1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)08c6903Prepare v5.0.0 release (#2238)