GeezerVison is showing github.com — fix(webapp): show the real app version instead of v0.0.0 in organization settings by matt-aitken · Pull Request #4611 · triggerdotdev/trigger.dev
Conversation
Summary
Since the move from the Remix compiler to Vite (#4188), the "App version" on the organization settings page shows v0.0.0 unless the image was built from a semver release tag (which bakes in BUILD_APP_VERSION). Self-hosted builds and any image built from main are affected. This restores the real version.
Root cause
The Vite SSR bundle resolves workspace packages to TS source via the @triggerdotdev/source condition, so @trigger.dev/core's VERSION constant is bundled as its raw "0.0.0" placeholder. scripts/updateVersion.ts still stamps the real version at build time, but only into the packages' dist output, which the bundle no longer reads. The old Remix compiler bundled the stamped dist, which is why this used to work.
The fix is a small Vite plugin that applies the same substitution to the source version modules of @trigger.dev/core and @trigger.dev/sdk during bundling. Beyond the settings page, this also restores real values in the trigger-version request header and the version attributes the bundled packages emit.
Verified by building the server bundle and confirming the VERSION constants carry the package versions, with no "0.0.0" occurrences left in the build output.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
…ion settings
The Vite SSR bundle resolves workspace packages to TS source, where the
VERSION constant is the unstamped 0.0.0 placeholder; the stamping script
only patches dist output, which the bundle never reads. A small Vite
plugin now performs the same substitution on the source version modules
of core and trigger-sdk during bundling, so the settings page and the
version headers the webapp sends carry the real version again.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
coderabbitai
Bot
commented
Aug 13, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|

No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: d8e5abe7-32f3-4fba-b761-19e8a674a0f8
📥 Commits
Reviewing files that changed from the base of the PR and between 72a3bb2 and 2bd6503.
📒 Files selected for processing (1)
apps/webapp/vite.config.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- apps/webapp/vite.config.ts
📜 Recent review details
⏰ Context from checks skipped due to timeout. (10)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (11, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 12)
- GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp
- GitHub Check: audit
- GitHub Check: code-quality / code-quality
- GitHub Check: audit
- GitHub Check: Analyze (actions)
- GitHub Check: Analyze (javascript-typescript)
Walkthrough
The Vite configuration reads versions from the core and trigger-sdk package manifests. It registers a plugin that replaces 0.0.0 constants in matching workspace version.ts modules during bundling. A server change note documents the organization settings app version correction.
Merge Risk: ⚪ Minimal · up to 2bd65
This localized build change restores accurate application version reporting and related version metadata; no actionable merge-blocking risk remains after normal checks and review.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name |
Status |
Explanation |
| Title check |
✅ Passed |
The title clearly identifies the primary fix: displaying the real app version in organization settings. |
| Description check |
✅ Passed |
The description explains the problem, root cause, solution, affected behavior, and verification steps, but omits the template checklist and issue reference. |
| Docstring Coverage |
✅ Passed |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Linked Issues check |
✅ Passed |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check |
✅ Passed |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
📝 Generate docstrings
- Create stacked PR
- Commit on current branch
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
fix/webapp-app-version-stamp
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
Comment @coderabbitai help to get the list of available commands.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Devin Review: No Issues Found
Devin Review analyzed this PR and found no bugs or issues to report.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
myftija
myftija approved these changes
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|