Skip to content

Draft changelog: Dynamic CI impact signal and action updates #456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mintlify merged 1 commit into from
Nov 4, 2026
Merged

Draft changelog: Dynamic CI impact signal and action updates #456

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions changelog/2026-11-04-dynamic-ci-impacts-and-action-updates.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Dynamic CI: Build tool impact signal and GitHub Action updates"
description: "Send your build tool's impact to Dynamic CI from Buildkite, show verdicts on GitHub Actions run summaries, and set up the action with a lighter checkout."
date: 2026-11-04
category: Dynamic CI
type: new-feature
---

**Dynamic CI can now use your build tool's view of a change, and the GitHub Action is easier to set up.** Dynamic CI is in private beta.

### New features

- **Send your build tool's impact from Buildkite.** If your build tool counts how much of the codebase a change affects, such as affected packages, send that count so Trunk runs broad changes. Requires the Buildkite plugin v0.1.8 or later. Ask us to turn the signal on. See the [Buildkite guide](/ci/dynamic-ci/getting-started/buildkite).

### Updates

- **Verdicts on the run summary.** Set `enable-annotation: true` on `trunk-io/dynamic-ci` to post each job's recommendation to the run's annotations and job summary. See the [action reference](/ci/dynamic-ci/dynamic-ci-action-reference).
- **Lighter checkout.** The action only needs `actions/checkout` with `clean: false`. When the checkout lacks the base or head commit, it reads the changed files with `github-token`.
- **Workflow checks.** Once your workflows call Dynamic CI, Trunk checks their YAML and flags problems. See the [GitHub Actions guide](/ci/dynamic-ci/getting-started/github-actions).
6 changes: 6 additions & 0 deletions changelog/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,12 @@ rss: true

### November 2026

<Update label="November 4, 2026" tags={["Dynamic CI"]}>
**[Dynamic CI: Build tool impact signal and GitHub Action updates](/changelog/2026-11-04-dynamic-ci-impacts-and-action-updates)**

Send your build tool's impact to Dynamic CI from Buildkite, show verdicts on GitHub Actions run summaries, and set up the action with a lighter checkout.
</Update>

<Update label="November 3, 2026" tags={["Code Quality"]}>
**[Code Quality: CLI 1.29.0](/changelog/2026-11-03-code-quality-cli-1-29-0)**

Expand Down
1 change: 1 addition & 0 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -967,6 +967,7 @@
{
"group": "November",
"pages": [
"changelog/2026-11-04-dynamic-ci-impacts-and-action-updates",
"changelog/2026-11-03-code-quality-cli-1-29-0"
]
},
Expand Down
Loading