chore: bump node from 7a4ef57 to 44bcbf4 in /docker/sandbox#515
Merged
Conversation
Bumps node from `7a4ef57` to `44bcbf4`. --- updated-dependencies: - dependency-name: node dependency-version: 25-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Owner
|
@coderabbitai review |
Aureliolo
approved these changes
Mar 17, 2026
Owner
Aureliolo
left a comment
Aureliolo
left a comment
There was a problem hiding this comment.
Reviewed: digest-only rebuild of node:25-slim (Debian base patches). No application-level changes. CI passing. Note: Node.js security release (2 HIGH, 5 MEDIUM, 2 LOW) scheduled for March 24 — expect a version bump PR then.
Aureliolo
added a commit
that referenced
this pull request
Mar 17, 2026
🤖 I have created a release *beep* *boop* --- ## [0.3.2](v0.3.1...v0.3.2) (2026-03-17) ### Features * **settings:** route structural data reads through SettingsService ([#525](#525)) ([289f604](289f604)) ### Bug Fixes * **cli:** add fallback arch detection in PowerShell installer ([#529](#529)) ([0250afb](0250afb)), closes [#521](#521) ### CI/CD * bump the minor-and-patch group with 2 updates ([#517](#517)) ([46bdd1a](46bdd1a)) * bump wrangler from 4.73.0 to 4.74.0 in /.github in the minor-and-patch group ([#511](#511)) ([903b71a](903b71a)) ### Maintenance * bump node from `7a4ef57` to `44bcbf4` in /docker/sandbox ([#515](#515)) ([3cbddd1](3cbddd1)) * bump python from `6a27522` to `584e89d` in /docker/backend ([#513](#513)) ([0715910](0715910)) * bump python from `6a27522` to `584e89d` in /docker/sandbox ([#514](#514)) ([787dfe1](787dfe1)) * bump the minor-and-patch group across 1 directory with 2 updates ([#527](#527)) ([e96c0d4](e96c0d4)) * bump the minor-and-patch group across 2 directories with 3 updates ([#512](#512)) ([b95ba3d](b95ba3d)) * **docker:** disable Mem0 telemetry in container config ([#531](#531)) ([9fc29eb](9fc29eb)) * improve GitHub issue templates with structured forms ([#528](#528)) ([4fb66cf](4fb66cf)), closes [#522](#522) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Aureliolo
added a commit
that referenced
this pull request
May 24, 2026
… gemini, 1 ci-bench) CI fixes: - restore CLI bench regression budget: hoist Validate / validateTunables check slices to package vars and replace closure-based bindings in resolveDurationTunables / resolveCountTunables with direct pointer setters; unroll per-section enumCheck / formatCheck / duration / byte slices in validate.go to inline if-chains. The closure + per-call slice allocations had pushed BenchmarkResolveTunables +32% and BenchmarkLoadExisting +57% allocs. Security alerts (3 dismissed): - CodeQL #515 cli/cmd/start.go:147 (false positive; safeDir comes from safeStateDir -> config.SecurePath, sanitiser cannot be traced past the assertComposeExists helper boundary) - CodeQL #516 cli/cmd/wipe.go:175 (same shape on requireComposeFile) - CodeQL #517 cli/internal/completion/install.go:381 (false positive; path is resolved from a fixed allowlist of shell config locations under the operator home dir, which is the entire point of completion uninstall) Reviewer feedback: - cleanup.go: collectCleanupCandidates now takes the existing *ui.UI instead of re-creating one; removeOldImages signature widened to (removed, freedB, hardFailures, ctxErr) so non "in use" docker rmi failures and ctx cancellation both surface as runtime errors - update_cleanup.go: runAutoCleanupRemovals returns ctxErr; reinstall next-step hint upgraded to HintNextStep - config.go: hintComposeRestart uses HintNextStep - config_dispatch.go: color/hints/output/timestamps readers now return the effective default (auto/auto/text/relative) instead of empty - doctor.go: classifyDoctorIssues honours --checks for the unfixable bucket (anyFixableCheckEnabled gate) - new.go: warnPartialScaffoldWrite emits the recovery hint via HintError so it survives every mode except --quiet - start.go: emitFineTuneSizeHint uses HintGuidance instead of HintTip - uninstall.go: GitHub releases reinstall hint + "container images still on disk" hint upgraded to HintNextStep - completion/install.go: probeShellProfile rel-check no longer rejects filenames that lexically start with ".." (e.g. "..config/profile.ps1") - compose/validate.go: validateDigestPins sorts keys before iterating so the returned error is deterministic - scaffold/writer.go: resolveOneTarget now resolves the deepest existing ancestor via EvalSymlinks and re-checks containment, so a symlinked subpath under absRoot cannot escape at write time - verify/dhi.go: readCosignPayload reads maxBundleBytes+1 and rejects oversize payloads explicitly (mirrors readAttestationStatement) - config/validate.go: validateMasterKey rejects an empty MasterKey when EncryptSecrets is true, exported as ErrMissingMasterKey; introduced LoadAllowMissingMasterKey + ValidateAllowMissingMasterKey so handleReinit can still recover an install whose persisted config predates the new invariant SKIP (verified factually wrong against current code): - Gemini "critical" errors.AsType typo on cli/cmd/update.go:360 -- Go 1.25+ stdlib added a generic errors.AsType helper; build + CI tests pass on Go 1.26 in this repo. golangci-lint actually surfaces the modernisation hint that callers SHOULD migrate to AsType. Tests updated where required: - cmd/* tests, config/* tests: explicit `state.EncryptSecrets = false` (or `encrypt_secrets: false` in JSON fixtures) where the test targets non-encryption behaviour, since the new MasterKey invariant rejects the DefaultState() baseline that those fixtures rely on. Issue: #2099
Aureliolo
added a commit
that referenced
this pull request
May 24, 2026
… gemini, 1 ci-bench) CI fixes: - restore CLI bench regression budget: hoist Validate / validateTunables check slices to package vars and replace closure-based bindings in resolveDurationTunables / resolveCountTunables with direct pointer setters; unroll per-section enumCheck / formatCheck / duration / byte slices in validate.go to inline if-chains. The closure + per-call slice allocations had pushed BenchmarkResolveTunables +32% and BenchmarkLoadExisting +57% allocs. Security alerts (3 dismissed): - CodeQL #515 cli/cmd/start.go:147 (false positive; safeDir comes from safeStateDir -> config.SecurePath, sanitiser cannot be traced past the assertComposeExists helper boundary) - CodeQL #516 cli/cmd/wipe.go:175 (same shape on requireComposeFile) - CodeQL #517 cli/internal/completion/install.go:381 (false positive; path is resolved from a fixed allowlist of shell config locations under the operator home dir, which is the entire point of completion uninstall) Reviewer feedback: - cleanup.go: collectCleanupCandidates now takes the existing *ui.UI instead of re-creating one; removeOldImages signature widened to (removed, freedB, hardFailures, ctxErr) so non "in use" docker rmi failures and ctx cancellation both surface as runtime errors - update_cleanup.go: runAutoCleanupRemovals returns ctxErr; reinstall next-step hint upgraded to HintNextStep - config.go: hintComposeRestart uses HintNextStep - config_dispatch.go: color/hints/output/timestamps readers now return the effective default (auto/auto/text/relative) instead of empty - doctor.go: classifyDoctorIssues honours --checks for the unfixable bucket (anyFixableCheckEnabled gate) - new.go: warnPartialScaffoldWrite emits the recovery hint via HintError so it survives every mode except --quiet - start.go: emitFineTuneSizeHint uses HintGuidance instead of HintTip - uninstall.go: GitHub releases reinstall hint + "container images still on disk" hint upgraded to HintNextStep - completion/install.go: probeShellProfile rel-check no longer rejects filenames that lexically start with ".." (e.g. "..config/profile.ps1") - compose/validate.go: validateDigestPins sorts keys before iterating so the returned error is deterministic - scaffold/writer.go: resolveOneTarget now resolves the deepest existing ancestor via EvalSymlinks and re-checks containment, so a symlinked subpath under absRoot cannot escape at write time - verify/dhi.go: readCosignPayload reads maxBundleBytes+1 and rejects oversize payloads explicitly (mirrors readAttestationStatement) - config/validate.go: validateMasterKey rejects an empty MasterKey when EncryptSecrets is true, exported as ErrMissingMasterKey; introduced LoadAllowMissingMasterKey + ValidateAllowMissingMasterKey so handleReinit can still recover an install whose persisted config predates the new invariant SKIP (verified factually wrong against current code): - Gemini "critical" errors.AsType typo on cli/cmd/update.go:360 -- Go 1.25+ stdlib added a generic errors.AsType helper; build + CI tests pass on Go 1.26 in this repo. golangci-lint actually surfaces the modernisation hint that callers SHOULD migrate to AsType. Tests updated where required: - cmd/* tests, config/* tests: explicit `state.EncryptSecrets = false` (or `encrypt_secrets: false` in JSON fixtures) where the test targets non-encryption behaviour, since the new MasterKey invariant rejects the DefaultState() baseline that those fixtures rely on. Issue: #2099
Aureliolo
added a commit
that referenced
this pull request
May 24, 2026
… gemini, 1 ci-bench) CI fixes: - restore CLI bench regression budget: hoist Validate / validateTunables check slices to package vars and replace closure-based bindings in resolveDurationTunables / resolveCountTunables with direct pointer setters; unroll per-section enumCheck / formatCheck / duration / byte slices in validate.go to inline if-chains. The closure + per-call slice allocations had pushed BenchmarkResolveTunables +32% and BenchmarkLoadExisting +57% allocs. Security alerts (3 dismissed): - CodeQL #515 cli/cmd/start.go:147 (false positive; safeDir comes from safeStateDir -> config.SecurePath, sanitiser cannot be traced past the assertComposeExists helper boundary) - CodeQL #516 cli/cmd/wipe.go:175 (same shape on requireComposeFile) - CodeQL #517 cli/internal/completion/install.go:381 (false positive; path is resolved from a fixed allowlist of shell config locations under the operator home dir, which is the entire point of completion uninstall) Reviewer feedback: - cleanup.go: collectCleanupCandidates now takes the existing *ui.UI instead of re-creating one; removeOldImages signature widened to (removed, freedB, hardFailures, ctxErr) so non "in use" docker rmi failures and ctx cancellation both surface as runtime errors - update_cleanup.go: runAutoCleanupRemovals returns ctxErr; reinstall next-step hint upgraded to HintNextStep - config.go: hintComposeRestart uses HintNextStep - config_dispatch.go: color/hints/output/timestamps readers now return the effective default (auto/auto/text/relative) instead of empty - doctor.go: classifyDoctorIssues honours --checks for the unfixable bucket (anyFixableCheckEnabled gate) - new.go: warnPartialScaffoldWrite emits the recovery hint via HintError so it survives every mode except --quiet - start.go: emitFineTuneSizeHint uses HintGuidance instead of HintTip - uninstall.go: GitHub releases reinstall hint + "container images still on disk" hint upgraded to HintNextStep - completion/install.go: probeShellProfile rel-check no longer rejects filenames that lexically start with ".." (e.g. "..config/profile.ps1") - compose/validate.go: validateDigestPins sorts keys before iterating so the returned error is deterministic - scaffold/writer.go: resolveOneTarget now resolves the deepest existing ancestor via EvalSymlinks and re-checks containment, so a symlinked subpath under absRoot cannot escape at write time - verify/dhi.go: readCosignPayload reads maxBundleBytes+1 and rejects oversize payloads explicitly (mirrors readAttestationStatement) - config/validate.go: validateMasterKey rejects an empty MasterKey when EncryptSecrets is true, exported as ErrMissingMasterKey; introduced LoadAllowMissingMasterKey + ValidateAllowMissingMasterKey so handleReinit can still recover an install whose persisted config predates the new invariant SKIP (verified factually wrong against current code): - Gemini "critical" errors.AsType typo on cli/cmd/update.go:360 -- Go 1.25+ stdlib added a generic errors.AsType helper; build + CI tests pass on Go 1.26 in this repo. golangci-lint actually surfaces the modernisation hint that callers SHOULD migrate to AsType. Tests updated where required: - cmd/* tests, config/* tests: explicit `state.EncryptSecrets = false` (or `encrypt_secrets: false` in JSON fixtures) where the test targets non-encryption behaviour, since the new MasterKey invariant rejects the DefaultState() baseline that those fixtures rely on. Issue: #2099
Aureliolo
added a commit
that referenced
this pull request
May 24, 2026
… gemini, 1 ci-bench) CI fixes: - restore CLI bench regression budget: hoist Validate / validateTunables check slices to package vars and replace closure-based bindings in resolveDurationTunables / resolveCountTunables with direct pointer setters; unroll per-section enumCheck / formatCheck / duration / byte slices in validate.go to inline if-chains. The closure + per-call slice allocations had pushed BenchmarkResolveTunables +32% and BenchmarkLoadExisting +57% allocs. Security alerts (3 dismissed): - CodeQL #515 cli/cmd/start.go:147 (false positive; safeDir comes from safeStateDir -> config.SecurePath, sanitiser cannot be traced past the assertComposeExists helper boundary) - CodeQL #516 cli/cmd/wipe.go:175 (same shape on requireComposeFile) - CodeQL #517 cli/internal/completion/install.go:381 (false positive; path is resolved from a fixed allowlist of shell config locations under the operator home dir, which is the entire point of completion uninstall) Reviewer feedback: - cleanup.go: collectCleanupCandidates now takes the existing *ui.UI instead of re-creating one; removeOldImages signature widened to (removed, freedB, hardFailures, ctxErr) so non "in use" docker rmi failures and ctx cancellation both surface as runtime errors - update_cleanup.go: runAutoCleanupRemovals returns ctxErr; reinstall next-step hint upgraded to HintNextStep - config.go: hintComposeRestart uses HintNextStep - config_dispatch.go: color/hints/output/timestamps readers now return the effective default (auto/auto/text/relative) instead of empty - doctor.go: classifyDoctorIssues honours --checks for the unfixable bucket (anyFixableCheckEnabled gate) - new.go: warnPartialScaffoldWrite emits the recovery hint via HintError so it survives every mode except --quiet - start.go: emitFineTuneSizeHint uses HintGuidance instead of HintTip - uninstall.go: GitHub releases reinstall hint + "container images still on disk" hint upgraded to HintNextStep - completion/install.go: probeShellProfile rel-check no longer rejects filenames that lexically start with ".." (e.g. "..config/profile.ps1") - compose/validate.go: validateDigestPins sorts keys before iterating so the returned error is deterministic - scaffold/writer.go: resolveOneTarget now resolves the deepest existing ancestor via EvalSymlinks and re-checks containment, so a symlinked subpath under absRoot cannot escape at write time - verify/dhi.go: readCosignPayload reads maxBundleBytes+1 and rejects oversize payloads explicitly (mirrors readAttestationStatement) - config/validate.go: validateMasterKey rejects an empty MasterKey when EncryptSecrets is true, exported as ErrMissingMasterKey; introduced LoadAllowMissingMasterKey + ValidateAllowMissingMasterKey so handleReinit can still recover an install whose persisted config predates the new invariant SKIP (verified factually wrong against current code): - Gemini "critical" errors.AsType typo on cli/cmd/update.go:360 -- Go 1.25+ stdlib added a generic errors.AsType helper; build + CI tests pass on Go 1.26 in this repo. golangci-lint actually surfaces the modernisation hint that callers SHOULD migrate to AsType. Tests updated where required: - cmd/* tests, config/* tests: explicit `state.EncryptSecrets = false` (or `encrypt_secrets: false` in JSON fixtures) where the test targets non-encryption behaviour, since the new MasterKey invariant rejects the DefaultState() baseline that those fixtures rely on. Issue: #2099
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 node from
7a4ef57to44bcbf4.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)