Bump peter-evans/create-pull-request from 6 to 8#1
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) from 6 to 8. - [Release notes](https://github.com/peter-evans/create-pull-request/releases) - [Commits](peter-evans/create-pull-request@v6...v8) --- updated-dependencies: - dependency-name: peter-evans/create-pull-request dependency-version: '8' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
milos85vasic
added a commit
that referenced
this pull request
Jul 7, 2026
…dary (§12.10/§11.4.131) HEAD c848a49 (remote==local). Records: pipeline fix + fleet security fixes (ssh-proxy/gateway/vault-IDOR/ notification-hardening) + real features (migrate+schema-per-service, xterm terminal, gateway real-proxy, pki/auth/mfa defect fixes) + 2 real backends implemented (notification delivery, port-forward SSH). S12 gateway-routes last in flight. Next: submodule-wiring phase (container-bridge/helixtrack/ai — repos verified exist) + operator-credential-blocked backends (billing/ai-cloud/push) + migrate rollout + coverage/final review. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
milos85vasic
added a commit
that referenced
this pull request
Jul 7, 2026
…tainerrt backend Add require+replace for digital.vasic.containers => ../../submodules/containers (fictitious module path, replace is mandatory). New internal/containerrt package wraps pkg/runtime.ContainerRuntime and adds RunFromImage (the one capability the upstream interface intentionally omits — creating a NEW container from an image), mirroring the documented precedent in digital.vasic.containers/pkg/brokertest. Detect() auto-detects the local runtime (Podman-first per module default, CONTAINER_RUNTIME_PRIORITY env override) and confirms rootless Podman 5.7.1 is found and available on this host. No handler wiring yet (next commit). Classification: project-specific (helix_terminator bridge #1 of 3).
milos85vasic
added a commit
that referenced
this pull request
Jul 7, 2026
…abrication §11.4.43/§11.4.115 RED-before-fix checkpoint. Extract BridgeStore interface (handler.go) so repo access is fakeable without a live Postgres (pure, behavior-preserving refactor — repository.Repository still satisfies it structurally, no repository.go changes). Handler.New now also takes a containerrt.Backend (nil-safe). Wire main.go to containerrt.Detect(). Add TestCreateBridge_DoesNotFabricateActiveStatus_WhenContainerNeverComesUp: fake backend proves (via Status) the container never started, yet the CURRENT (unfixed) CreateBridge still writes status "active" and returns 201. Captured RED evidence (this commit, test FAILS): "201" is not greater than or equal to "500" response body contains "status":"active" repo.created is non-empty (a bridge WAS persisted for a container that never came up) Next commit implements the real runtime.Status reconciliation and reruns this exact test to GREEN. Classification: project-specific (helix_terminator bridge #1 of 3).
milos85vasic
added a commit
that referenced
this pull request
Jul 7, 2026
…eleteBridge against real runtime.Status GREEN — TestCreateBridge_DoesNotFabricateActiveStatus_WhenContainerNeverComesUp now PASSes (was RED in the prior commit). CreateBridge: bringUp() attaches to an existing container by req.ContainerID (starts it if not running) or runs a brand-new one from req.Image via containerrt.Backend.RunFromImage; persisted Status derives from the REAL runtime.Status result (containerrt.StatusFromState) — "active" ONLY when the runtime confirms StateRunning. A container that fails to come up returns 502, no row persisted (no unconditional "active"). GetBridge/ListBridges: reconcile() re-checks h.backend.Status for every returned bridge and rewrites Status in the response (+ best-effort UpdateBridge persistence) so a stopped/removed container never still reads "active". DeleteBridge: Stop()+Remove() the backing container (WithForceRemove + WithRemoveVolumes, idempotent against an already-gone container) before deleting the row. If the runtime is unavailable (backend nil or IsAvailable==false), CreateBridge fails honestly with 503 rather than fabricating status. Classification: project-specific (helix_terminator bridge #1 of 3).
milos85vasic
added a commit
that referenced
this pull request
Jul 7, 2026
…27) + fix ContainerID round-trip bug it caught
Add optional trailing cmd to containerrt.Backend.RunFromImage (backward-
compatible variadic) + optional model.CreateContainerBridgeRequest.Command:
needed because a real-host FACT (verified via direct `podman run -d
busybox:latest`, captured before writing any test per §11.4.6) shows bare
busybox exits almost immediately (sh reads EOF on closed stdin under -d) —
real application images normally have a long-running entrypoint of their
own, busybox specifically needs a command override to stay up for the test.
TestIntegration_ContainerBridge_RealPodman (build tag `integration`) drives
CreateBridge -> GetBridge -> DeleteBridge through the real HTTP handlers
wired to a REAL auto-detected Podman runtime (no fake ContainerRuntime in
this test, per §11.4.27): creates a real busybox container, cross-checks
the API's reported status against real `podman inspect`/`podman ps -a`
sink-side evidence (§11.4.13/§11.4.69), stops the container out-of-band and
confirms GetBridge's reconciliation demotes it off "active", then confirms
DeleteBridge really Stop+Removes it. Container is force-removed in
t.Cleanup on every exit path (§11.4.14) -- verified zero orphans left after
the run (podman ps -a).
This test caught a REAL bug on first run (not a fabricated demo): bringUp's
create-branch returned RunFromImage's runtime-assigned hash ID instead of
the client-given `name`, so a subsequent GetBridge/DeleteBridge using the
bridge's stored ContainerID would not resolve to a valid identifier
consistently with the attach-existing-container branch. Root-caused per
§11.4.102 and fixed at source: bringUp now always returns `name` (the
podman/docker container name == req.ContainerID or the generated
"bridge-<uuid>"), matching the attach branch and every subsequent
Status/Stop/Remove call. Re-ran the same integration test after the fix:
PASS.
Uses `t.Context()` (Go 1.24+, module targets go 1.25.0).
Evidence commands + output:
GOWORK=off GOMAXPROCS=2 go test -tags=integration -p 2 -count=1 -v \
-run TestIntegration_ContainerBridge_RealPodman ./internal/handler/...
=> PASS (13.27s)
podman ps -a --filter name=cbs-integration --format '{{.Names}}' => empty (no orphans)
Classification: project-specific (helix_terminator bridge #1 of 3).
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 peter-evans/create-pull-request from 6 to 8.
Release notes
Sourced from peter-evans/create-pull-request's releases.
... (truncated)
Commits
5f6978ffix: retry post-creation API calls on 422 eventual consistency errors (#4356)d32e88dbuild(deps-dev): bump the npm group with 3 updates (#4349)8170bccbuild(deps-dev): bump handlebars from 4.7.8 to 4.7.9 (#4344)0041819build(deps): bump picomatch (#4339)b993918build(deps-dev): bump flatted from 3.3.1 to 3.4.2 (#4334)36d7c84build(deps-dev): bump undici from 6.23.0 to 6.24.0 (#4328)a45d1fbbuild(deps): bump@tootallnate/onceand jest-environment-jsdom (#4323)3499eb6build(deps): bump the github-actions group with 2 updates (#4316)3f3b473build(deps): bump minimatch (#4311)6699836build(deps-dev): bump the npm group with 2 updates (#4305)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)