[Fix] Deployment images return 500 after release-history update - #1898
Merged
Conversation
Contributor
mrubens
marked this pull request as ready for review
August 30, 2026 22:47
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 30, 2026 22:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
CHANGELOG.mddirectly into the final application image at the path used by release history.Why this change was made
PR #1893 added
../../CHANGELOG.mdto the web app's tracing includes. The first two publish runs after that change failed deployment acceptance because the standalone image omitted transitive dependencies forioredis,pino-pretty, andbullmq, causing the web smoke request to return HTTP 500.Impact
Deployment images can load all traced server dependencies while continuing to serve release history from the bundled changelog. A clean production web build, focused release-history tests, type checks, lint, and the full pre-push suite passed. Docker-backed image and acceptance validation could not run locally because the sandbox does not expose a Docker socket; the publish workflow will exercise that exact path.