fix(cli): sort bundle output files for deterministic task-to-file attribution

[okxint]

Summary

When getBundleResultFromBuild iterates Object.entries(result.metafile.outputs), the order is not guaranteed by the spec. On some Node versions and esbuild configurations, task files appear in arbitrary order. When registerResources then iterates files to attribute tasks to their source, a task defined in child.ts (imported by parent.ts) can end up attributed to parent.ts if its output appears first — breaking per-file grouping in the dashboard.

Fixes #4495.

Change

Sort files by entry path (alphabetically) after the loop, before returning, so attribution is deterministic regardless of Object.entries order.

+  files.sort((a, b) => a.entry.localeCompare(b.entry));
+
   if (!configPath) {
     return undefined;
   }

How to test

Deploy a project that has a parent task importing a child task in a separate file. Confirm both tasks appear under their correct source files in the dashboard across multiple deploys.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5e1f25f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 26 packages

Name	Type
trigger.dev	Patch
@internal/dashboard-agent	Patch
@trigger.dev/build	Patch
@trigger.dev/core	Patch
@trigger.dev/python	Patch
@trigger.dev/react-hooks	Patch
@trigger.dev/redis-worker	Patch
@trigger.dev/rsc	Patch
@trigger.dev/schema-to-json	Patch
@trigger.dev/sdk	Patch
@trigger.dev/database	Patch
@trigger.dev/otlp-importer	Patch
@trigger.dev/rbac	Patch
@trigger.dev/sso	Patch
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/llm-model-catalog	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/run-store	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/tsql	Patch
@internal/sdk-compat-tests	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Hi @okxint, thanks for your interest in contributing!

This project requires that pull request authors are vouched, and you are not in the list of vouched users.

This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details.

[devin-ai-integration]

Devin Review found 2 potential issues.

[devin-ai-integration]

🟡 Release note text describes internals instead of user impact

The release note for this change is written in implementation terms, naming internal mechanics (Object.entries in .changeset/bundle-deterministic-file-order.md:5) instead of a plain user-facing sentence, so shipped release notes will violate the repository's changeset writing rules.
Impact: Users reading the release notes see internal jargon rather than a clear description of what changed for them.

Rule from AGENTS.md on changeset wording

AGENTS.md states: "Write the description for users, not maintainers. Both changesets and .server-changes/ notes ship verbatim in user-visible release notes. Lead with what changed for the user - one plain sentence describing behavior, not implementation, and never naming internal tools or infra." The current note leads with "non-deterministic task-to-file attribution" and cites Object.entries iteration order and internal registration order.

Suggested change

	Fix non-deterministic task-to-file attribution when multiple tasks share an output bundle. `Object.entries` iteration order is not guaranteed, so tasks defined in imported files could be attributed to the wrong source file. Files are now sorted by entry path before registration.
	Tasks now consistently appear under the file they are defined in, instead of sometimes being grouped under a file that imports them.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔍 Alphabetical sort makes attribution deterministic but not necessarily correct

Sorting files by entry path only guarantees a stable order; it does not guarantee that a file defining a task is imported before a file that imports it. registerResources (packages/cli-v3/src/indexing/registerResources.ts:11-14) attributes every task registered during an import to the currently-imported entry, so a parent file that sorts earlier than its child (e.g. trigger/a-parent.ts importing trigger/z-child.ts) will still claim the child's tasks. The PR makes the misattribution consistent rather than eliminating it; a real fix would need to attribute tasks by the source file recorded at registration time (or import leaf modules first based on the metafile import graph).

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6020acfd-9d27-4b4f-baa3-ae41f7742bb7

📥 Commits

Reviewing files that changed from the base of the PR and between ca9a74e and 5e1f25f.

📒 Files selected for processing (2)

• .changeset/bundle-deterministic-file-order.md
• packages/cli-v3/src/build/bundle.ts

---

Walkthrough

Bundle entry files are now sorted alphabetically by their entry path before the bundle result is returned. A patch changeset documents the deterministic ordering and task-to-file attribution behavior.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}