fix(extensions): prevent audiowaveform binary removal

[nicktrn]

We apt update and install later. Doing this early meant --fix-broken would uninstall the package again.

[changeset-bot]

🦋 Changeset detected

Latest commit: 7927ec3

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

This PR includes changesets to release 23 packages

Name	Type
@trigger.dev/build	Patch
trigger.dev	Patch
@trigger.dev/python	Patch
d3-chat	Patch
references-d3-openai-agents	Patch
references-nextjs-realtime	Patch
@trigger.dev/core	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
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/zod-worker	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

[coderabbitai]

Walkthrough

The pull request adds a changeset entry documenting a patch release for @trigger.dev/build. The corresponding code change removes the apt-get install -y --fix-broken instruction from the audiowaveform extension's Docker build layer steps, simplifying the installation sequence without altering other instruction blocks or control flow.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify the rationale for removing apt-get install -y --fix-broken — ensure the underlying package installation issue it addressed is no longer present
• Confirm the audiowaveform extension builds successfully without this command
• Validate that the changeset entry accurately reflects the fix and uses appropriate versioning

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete relative to the provided template. While the single-sentence explanation provided is directly on-topic and helpful in understanding the technical fix, it is missing most required template sections including the issue reference (Closes #), the checklist items, the testing section, and a proper changelog entry. The description lacks the structured information needed to follow the repository's contribution standards.	The PR description should be updated to include all required template sections: add an issue reference at the top, complete the checklist confirming adherence to the contributing guide and testing, provide a detailed testing section describing the specific steps taken to verify the fix, and expand the changelog section with a formatted description of the changes. The brief technical explanation currently provided could be incorporated into the testing or changelog sections.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "fix(extensions): prevent audiowaveform binary removal" is fully related to the main change in the changeset. The title clearly identifies the fix (preventing binary removal) and the affected component (extensions), which directly aligns with the code change that removes the problematic apt-get install -y --fix-broken instruction from the audiowaveform build steps. The title is concise, specific, and uses conventional commit format appropriately.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/audiowaveform

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.changeset/perfect-rice-judge.md (1)

1-5: Consider adding context about the fix in the changelog entry.

The description is brief and vague. While the changeset format is correct, a more detailed message would help future developers and changelog readers understand what the issue was and how it was resolved.

Apply this diff to improve changelog clarity:

---
"@trigger.dev/build": patch
---

-Fix broken audiowaveform extension
+Fix audiowaveform binary removal during Docker build by reordering apt operations

This gives readers better context about what was broken and why the fix works.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf6735b and 7927ec3.

📒 Files selected for processing (2)

• .changeset/perfect-rice-judge.md (1 hunks)
• packages/build/src/extensions/audioWaveform.ts (0 hunks)

💤 Files with no reviewable changes (1)

• packages/build/src/extensions/audioWaveform.ts

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: zvictor
PR: triggerdotdev/trigger.dev#1686
File: packages/build/src/extensions/python.ts:110-116
Timestamp: 2025-02-10T10:56:31.402Z
Learning: In Docker build contexts for Trigger.dev extensions, avoid over-engineering security measures when handling user-provided configuration (like Python requirements) as the build context is already isolated and the content is user-controlled.

Learnt from: zvictor
PR: triggerdotdev/trigger.dev#1686
File: packages/build/src/extensions/python.ts:85-87
Timestamp: 2025-02-10T10:54:17.345Z
Learning: In Python-related Dockerfiles for trigger.dev, avoid adding explicit Python version pinning as the base image already provides conservative version management. Additional pinning would unnecessarily slow down builds.

📚 Learning: 2025-08-18T10:07:17.368Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-08-18T10:07:17.368Z
Learning: Applies to trigger.config.ts : Declare build options and extensions (external, jsx, conditions, extensions) via the build block in trigger.config.ts rather than custom scripts

Applied to files:

• .changeset/perfect-rice-judge.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)

• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)