Skip to content

ci: bump agents-chat-action to v0.5.1 in doc-check (backport 2.34) - #30850

Merged
droopy4096 merged 1 commit into
release/2.34from
ci/doc-check-agents-chat-action-v0.5.1-release-2.34
Oct 15, 2026
Merged

droopy4096 merged 1 commit into
release/2.34from
ci/doc-check-agents-chat-action-v0.5.1-release-2.34

Conversation

@coder

@coder coder Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Bumps the pinned coder/agents-chat-action in .github/workflows/doc-check.yaml on release/2.34 from v0 to v0.5.1 (9b3ac42). Same change as #29732 on main.

Why

The Analyze PR for Documentation Updates Needed job fails on every PR into release/2.34 (e.g. #30811) with Coder API error: Not Found. The pinned version calls /api/experimental/chats, which #29548 removed after the chat API moved to /api/v2 (#28496). v0.5.1 calls /api/v2/chats.

v0.5.1 accepts every input this workflow passes (its inputs are a superset of v0.3.0's), so no other workflow changes are needed. The doc-check run on this PR is the end-to-end test.

Changes

  • .github/workflows/doc-check.yaml: one uses: line.

Related: ENT-210 (surfaced on the Go 1.26.9 backports).

Opened by Superblink on behalf of @droopy4096.

doc-check on release/2.34 pins coder/agents-chat-action@f0b975f (v0), which calls the
/api/experimental chat routes removed in #29548, so every run fails with
"Coder API error: Not Found". v0.5.1 calls /api/v2 and accepts the same
inputs. Same change as #29732 on main.
@coder
coder Bot requested a review from jdomeracki-coder as a code owner October 15, 2026 14:49
@github-actions github-actions Bot added the community Pull Requests and issues created by the community. label Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

👋 Hey @coder[bot]!

This PR is targeting the release/2.34 release branch, but its title does not start with fix: or fix(scope):.

Only bug fixes should be cherry-picked to release branches. If this is a bug fix, please update the PR title to match the conventional commit format:

fix: description of the bug fix
fix(scope): description of the bug fix

If this is not a bug fix, it likely should not target a release branch.

@linear-code

linear-code Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

ENT-212

ENT-215

droopy4096 added a commit that referenced this pull request Oct 15, 2026
… 2.34) (#30858)

<!--

If you have used AI to produce some or all of this PR, please ensure you
have read our [AI Contribution
guidelines](https://github.com/coder/coder/blob/main/contributing/AI_CONTRIBUTING.md)
before submitting.

-->

Removes the nix dev image from `.github/workflows/dogfood.yaml` on
`release/2.34`, aligning it with `release/2.35` and later (`["22.04",
"26.04"]`). Tracked in
[ENT-214](https://linear.app/codercom/issue/ENT-214).

## Why

`build_image (nix)` fails on every `release/2.34` PR that triggers the
dogfood workflow (e.g. #30811):

`error: cannot download google-chrome-stable_143.0.7499.169-1_amd64.deb
from any mirror` (HTTP 404)

The nix dev image includes `google-chrome` from the `nixos-25.05`
nixpkgs pinned in this branch's `flake.lock`. Google only serves recent
Chrome builds, so the pinned `.deb` is gone. `main` removed the nix
image in #26022 after 2.34 was cut, so only this branch still builds it.
Bumping nixpkgs instead would change many packages on an old release
branch, and the Chrome pin would go stale again.

## Changes

`.github/workflows/dogfood.yaml` only, mirroring the workflow part of
#26022:

- Drop `nix` from the `build_image` matrix.
- Remove the nix-only steps: Nix install, `cache-nix-action`, `nix build
.#dev_image`, and the `codercom/oss-dogfood-nix` push.
- Drop the `matrix.image-version != 'nix'` guards, which are now always
true.
- Drop the `flake.nix` / `flake.lock` path triggers, since no job in
this workflow uses the flake anymore.
- Update comments that mentioned the nix image.

Not touched, to keep the backport small: `flake.nix` (`dev_image`
output), `nix/docker.nix`, and the nix image option in
`dogfood/coder/main.tf`. None of them is used by CI after this change.

## Notes

- `Analyze PR for Documentation Updates Needed` fails here for an
unrelated reason (outdated `agents-chat-action` pin, fixed by #30850 /
[ENT-212](https://linear.app/codercom/issue/ENT-212)).
- `chromatic` fails on all `release/2.34` PRs ("No app with code ...
found"), also unrelated.
@droopy4096
droopy4096 merged commit 3a5d040 into release/2.34 Oct 15, 2026
49 of 50 checks passed
@droopy4096
droopy4096 deleted the ci/doc-check-agents-chat-action-v0.5.1-release-2.34 branch October 15, 2026 17:57
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

community Pull Requests and issues created by the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants