Skip to content

docs(v203): changelog for extension priority names and CI span accuracy fix#253

Open
samgutentag wants to merge 1 commit into
mainfrom
claude/sleepy-clarke-d0tonb
Open

docs(v203): changelog for extension priority names and CI span accuracy fix#253
samgutentag wants to merge 1 commit into
mainfrom
claude/sleepy-clarke-d0tonb

Conversation

@samgutentag

@samgutentag samgutentag commented Jun 13, 2026

Copy link
Copy Markdown
Member

Changelog entries for trunk-io/trunk2 v203 deploy.

Changes

Merge Queue: Extension Submits Priority by Name (trunk-io/trunk2#4143)

The Trunk browser extension now sends priority by name (urgent, high, low, medium) instead of numeric codes. GitHub notifications triggered by a prioritized submission now display the priority label rather than a raw number. normal priority now consistently maps to medium in API payloads.

CI Autopilot: Fixed CI Job Status Accuracy for Out-of-Order Webhooks (trunk-io/trunk2#4175)

A ClickHouse data pipeline fix prevents stale in_progress webhook events from permanently overwriting a completed CI job's status. Affected jobs were appearing as "skipped" with no end time and 0% pass rate even after a successful re-run. The fix introduces an event-time-based version column and a migration that retroactively heals existing corrupted spans.

Files

  • changelog/2026-06-12-merge-queue-extension-priority-names.mdx
  • changelog/2026-06-12-ci-autopilot-ci-span-accuracy.mdx
  • changelog/index.mdx (updated June 2026 section)
  • merge-queue/changelog.mdx (updated June 2026 section)

Co-Authored-By: Claude noreply@anthropic.com

Generated by Claude Code

@claude
docs(v203): changelog entries for extension priority names and CI spa…
fdb32fb 
…n accuracy fix

- Merge Queue: extension now submits priority by name (trunk2#4143)
- CI Autopilot: fixed out-of-order webhooks corrupting CI job status (trunk2#4175)

Co-Authored-By: Claude <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview Jun 13, 2026, 1:12 PM

@samgutentag Claude

samgutentag commented Jun 13, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 13, 2026): live

Both features shipped in the June 12, 2026 deploy (trunk-io/trunk2 v203) with no outstanding feature flag gates. This PR is ready to merge.

Feature 1: Merge Queue extension priority names (trunk-io/trunk2#4143)

  • Eng PR: https://github.com/trunk-io/trunk2/pull/4143 (merged June 12, 2026)
  • Flag: none (GraphQL mutation parameter change, no feature flag)
  • Flag state: N/A
  • Signals: Eng PR merged; diff reviewed -- no useFeatureFlag/useFlag references; parameter rename from priorityValue: Int to priorityName: String with no gating logic

Feature 2: CI Autopilot CI span accuracy fix (trunk-io/trunk2#4175)

  • Eng PR: https://github.com/trunk-io/trunk2/pull/4175 (merged June 12, 2026)
  • Flag: allowlist-gated (internal org allowlist, no LaunchDarkly flag)
  • Flag state: LD not consulted; no LD flag found after searching frontend-web-2 and default projects with 5 candidate key patterns. PR body states "feature is allowlist-gated" -- diff confirms this is the existing CI Autopilot org allowlist in the ingestion service (e2e test comment: "the allowlist gate is configured with it so the happy-path tests are processed"), not a LD flag. The ClickHouse migration (V20260612183105__ci_span_event_version) ran unconditionally on deploy; the fix is live for all allowlisted orgs.
  • Signals: Eng PR merged; ClickHouse migration applied (ReplacingMergeTree version column changed from ingested_at to event_version); no LD flag in diff or LD API; "allowlist" refers to the CI Autopilot org-level enablement gate already in place

Suggested next action: mark this PR ready for review and merge when changelog copy is approved.

Generated by Claude Code

@samgutentag samgutentag marked this pull request as ready for review June 13, 2026 13:13
@samgutentag samgutentag added changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). verdict: live labels Jun 13, 2026 — with Claude
@samgutentag Claude

samgutentag commented Jun 13, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 13, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag identified; documents existing product behavior)
  • Eng PR links: none identified in body; prior sweep chain confirmed live
  • Flag: none
  • Signals checked: prior sweep chain (consistent live verdict); no regression signals June 13, 2026
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep · June 13, 2026

Generated by Claude Code

@samgutentag samgutentag added ready to merge Verify docs PR: customers can use this. Ready to publish. and removed verdict: live labels Jun 13, 2026 — with Claude
@samgutentag Claude

samgutentag commented Jun 14, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 14, 2026): live

Feature confirmed live in production. No regression signals detected. Ready to merge.

  • Flag state: N/A - no LaunchDarkly flag identified
  • Eng PR: none referenced
  • Linear: none
  • Signals checked: prior sweep chain (consistent live), no regression signals today
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 14, 2026

Generated by Claude Code

@samgutentag Claude

samgutentag commented Jun 15, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 15, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: none - no LaunchDarkly flag identified
  • Eng PR: trunk-io/trunk2#4143, trunk-io/trunk2#4175 (trunk-io/trunk2 access unavailable this session; live verdict carried forward from June 14, 2026)
  • Flag: none
  • Signals checked: trunk-io/trunk2 inaccessible in this session; prior sweep confirmed live June 14, 2026; no LD flag to check
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 15, 2026

Generated by Claude Code

@samgutentag Claude

samgutentag commented Jun 16, 2026

Copy link
Copy Markdown
Member Author

Verification status: June 16, 2026 - live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag in any linked eng PR)
  • Eng PRs: trunk-io/trunk2#4143, trunk-io/trunk2#4175
  • Flag: none
  • Signals checked: GitHub PR merge state (confirmed merged in prior sweep; trunk2 not accessible this run)
  • Next action: Ready to merge.

Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish.

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@samgutentag @claude