What happened
Dagger’s November 10, 2026 announcement introduces Dagger for GitLab. The stated capability is narrow but consequential: Dagger checks can run on every GitLab merge request without a GitLab CI job or a GitLab runner. Rather than asking teams to configure a conventional GitLab CI pipeline for those checks, the product attaches Dagger’s checking workflow to the merge-request process.
Dagger says the checks run through Dagger Cloud. In a conventional GitLab CI arrangement, a pipeline job is defined in GitLab and a runner executes that job. The company positions this launch as an alternative path for Dagger checks: the GitLab merge request remains the review surface, while the GitLab CI job and runner are not part of the execution path described in the announcement. The announcement does not explain the technical connection between a GitLab project and Dagger Cloud.
The release follows two closely related announcements on Dagger’s blog. On October 29, Dagger announced Dagger for GitHub, saying that checks run directly from GitHub without GitHub Actions; that listing also mentions managed engines, a distributed cache, and high-resolution traces. On November 4, Dagger announced Dagger for Entire, a Git forge for agents and humans, with checks running before and after push and a shared cache. Those are features described for the respective GitHub and Entire launches. Dagger’s GitLab listing does not say whether its GitLab integration includes the same capabilities.
The announcement identifies neither a price nor a plan requirement for Dagger for GitLab. It also does not state a rollout phase, supported GitLab editions, regional availability, usage limits, or a list of check types. Dagger’s claim is limited to running Dagger checks on every merge request without the two GitLab CI components. Teams considering the integration will need to confirm the operational details before making it a production merge gate.
What the archive adds
New Runtime covered Dagger’s GitHub checks integration on October 31, 2026. That earlier launch ran checks through Dagger Cloud without GitHub Actions. Dagger for GitLab is a new platform expansion of the same product direction, rather than a restatement of the GitHub event.
Trend signal
This tentatively supports New Runtime’s verification-ownership shift: developer platforms are expected to attach verification evidence and provenance to agent-authored changes. Dagger’s announcement establishes that checks can run on each GitLab merge request, which moves verification closer to the review event. It does not, however, describe the evidence produced, its provenance, or the review controls around it. The direction fits, but the implementation remains unproven.
Why now
The timing follows a concentrated run of forge integrations. Dagger announced its GitHub option on October 29, its Entire option on November 4, and the GitLab option on November 10. The sequence suggests that Dagger is extending one checks model across code-review systems rather than presenting GitLab support as an isolated CI feature.
Connections to other events
New Runtime’s October 31 note on Dagger for GitHub covered the removal of GitHub Actions from the path for Dagger checks. An earlier New Runtime note from the same date covered GitHub Agent Merge, where Copilot watches pull requests for failing Actions workflows or merge conflicts. Both developments put more verification activity around the pull-request boundary, although they use different products and mechanisms.
Why it matters
GitLab teams already using Dagger may be able to put Dagger-based checks into merge-request review without maintaining a GitLab CI job and runner for that purpose. That can matter when a team wants one checking system across local development and hosted code review, rather than reproducing pipeline definitions and execution arrangements in each forge.
The important change is not that merge requests receive checks; GitLab already supports that workflow. It is the relocation of orchestration. The team trades part of its GitLab CI setup for an execution dependency on Dagger Cloud. That trade may reduce forge-specific pipeline maintenance, but it also makes the behavior of permissions, failure reporting, logs, access controls, and service availability central to the review process. The announcement establishes the integration’s promise, not its fit for every GitLab project.
Limits and uncertainty
Dagger does not specify setup steps, required GitLab permissions, supported GitLab editions, pricing, plan eligibility, rollout conditions, or usage limits. The announcement does not describe the execution environment, status reporting, logs, failure handling, or how reviewers interact with results. It also reports no performance, reliability, security, or adoption measurements. New Runtime has not independently tested the integration. Teams should validate these operational details, particularly the merge-gate behavior, before making the checks mandatory.
Reader takeaway
Dagger for GitLab brings Dagger checks to each merge request without a GitLab CI job or runner, with Dagger Cloud handling the stated execution path. It is a meaningful option for a GitLab team already committed to Dagger, but not yet a fully specified replacement for a production CI setup. Confirm the integration’s access, reporting, limits, and operating model first.