Repository navigation
Description
What happens
The GitLab CI scaffold pulls the runner image from main, even when the project pins a fullsend release:
fullsend-agent.yml:108,fullsend-dispatcher.yml:31andfullsend-poll.yml:12(underinternal/scaffold/fullsend-repo-gitlab/.gitlab/ci/) all useghcr.io/fullsend-ai/fullsend-runner:dev.runner-image.ymlmovesdevon everymainpush that touchesimages/runner/**,openshell-version.sh,go.mod/go.sumor the workflow.gitlab.fullsend_refpins only the CLI.install-fullsend-cli.shreceives it through the__FULLSEND_VERSION__placeholder; the image is not templated.
So a GitLab project on a release runs that release's CLI with whatever OpenShell, gh, gitleaks, pre-commit, Go and gcloud main last built. GitHub users get the action and tools of the tag they pin.
This is how the OpenShell 0.1.4 bump (#8299) reached every GitLab runner within the hour, with no release or user action (#8564). #8566 now lets the runner VM install the job image's OpenShell version, so that exact failure should not recur. The release mismatch remains: a project pinned to an older release still gets main's OpenShell, and the next one is close, since Renovate #8738 (OpenShell 0.1.5) is open. When it merges, every GitLab install moves to 0.1.5 at once, before any release is tested with it.
:dev was introduced by #6483 "as a temporary measure until the scaffolds can be updated to pin a specific release version". Nothing outside the GitLab scaffold pulls fullsend-runner:dev; the GitHub action does not use the runner image.
What should happen
Before GitLab is announced as production-ready, the runner image should follow fullsend_ref:
- A release ref (the default) renders
ghcr.io/fullsend-ai/fullsend-runner:X.Y.Zinto all three templates, using the same renderer that fills__FULLSEND_VERSION__(internal/scaffold/installfiles.go,internal/repos/remote_scaffold.go). fix(#8564)!: let GitLab runners serve multiple OpenShell pins #8566 already verifies that a release-tagged image's revision matches thevX.Y.Ztag. latestshould resolve to a concrete release at install time, or be documented as tracking releases, notmain.- Tracking
mainstays possible only as an explicit opt-in for maintainers and early testers (for example arunner_image: devsetting), not the default. An untagged commit ref cannot map to an image automatically, because the image is built only for commits that touch the runner paths. repos status/ convergence should report drift when the rendered image tag andfullsend_refdisagree, so existing trial installs are upgraded byrepos install.- Docs (
configuring-gitlab.md,hack/gitlab-runner-vm/README.md) state which image a project runs and how it changes on upgrade.
Acceptance checks
- A fresh install pinned to a release renders the matching
fullsend-runner:X.Y.Zin the agent, dispatcher and poll templates. - Merging a runner-image change to
maindoes not change the image a release-pinned GitLab project runs. - Upgrading
fullsend_refre-renders the image tag in the same convergence run. - The
devopt-in still works and is called out as unsupported for production.
Timing
Ideally this lands before #8738 merges; otherwise #8738 ships OpenShell 0.1.5 to GitLab trial installs straight from main.
cc @ggallen — this blocks calling GitLab production-ready. Your call on timing relative to #8738 and the open GitLab work.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
fullsend-ai-triage commentedon Oct 27, 2026
🤖 Finished Triage · ✅ Success · Started 3:38 PM UTC · Completed 3:40 PM UTC
Commit:
ea70926· View workflow run →Runtime: claude · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.19
fullsend-ai-triage commentedon Oct 27, 2026
Triage found this actionable as written. No existing PR or duplicate issue was found. Related #6483, #8564 and #8730 are closed and #8566 is merged. #8738 is still open and is a timing concern rather than a blocker.
Fix targets verified in this repo: the
:devimage reference is at the cited lines in the three GitLab CI scaffold templates. The version placeholder is rendered ininternal/repos/remote_scaffold.go.internal/repos/gitlab_trigger_dispatch_gate.goalso handles the marker for install-script comparison, so it will need to stay consistent with any new placeholder. The docs named in the issue both exist. The GitLab CI scaffolds are not GitHub workflow files, so the workflow-change limitation does not apply.Points for the implementer to settle:
X.Y.Zwithout thevprefix thatfullsend_refcarries. Confirm the tag format when templating.runner_image: dev. Document it in the config reference, and also in the GitLab docs listed in the issue.:dev.Proposed test case:
The issue asks the maintainer to decide timing relative to #8738. This triage does not make that call.
Next steps:
/fs-code— agent creates a PR to implement this issue/fs-code <your instruction>— agent implements with your specific guidanceggallen commentedon Oct 27, 2026
/fs-code
fullsend-ai-coder commentedon Oct 27, 2026
🤖 Finished Code · ✅ Success · Started 11:47 PM UTC · Completed 12:10 AM UTC
Commit:
f3b9d98· View workflow run →Runtime: claude · Model: opus → claude-opus-5-5 · Effort: high · Cost: $4.17
fix(fullsend-ai#8865)!: pin GitLab runner image to fullsend_ref inste…
Merge pull request fullsend-ai#8878 from fullsend-ai/agent/8865-pin-g…