chore: bump version to 0.4.0 - #119
Merged
Merged
Conversation
Covers the three changes just merged: the SSR 500 fix on /request/<id> (#116), per-chain query resilience so one dead subgraph stops zeroing all payment data (#117), and server-rendering the request page (#118). A minor bump rather than a patch, since #118 changes how that route renders and #117 changes the query layer's failure behaviour. package-lock.json is regenerated. The diff is only the two version fields — no dependency was upgraded as a side effect. The version badge in the footer reads this value from package.json, so it picks the change up with no code change.
Greptile SummaryUpdates the application release metadata from version 0.3.4 to 0.4.0.
Confidence Score: 5/5The PR appears safe to merge because the release metadata is consistent and no dependency resolution changed. The manifest and lockfile apply the same version bump, while scripts, dependency declarations, resolved package versions, and integrity data remain unchanged. Important Files Changed
Reviews (1): Last reviewed commit: "chore: bump version to 0.4.0" | Re-trigger Greptile |
LeoSlrRf
approved these changes
Jul 29, 2026
MantisClone
approved these changes
Jul 29, 2026
Contributor
Author
Merge activity
|
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.
Bumps the version
0.3.4→0.4.0and regenerates the lockfile.Covers the three fixes just merged:
/request/<id>URL returned HTTP 500 (html2pdf.jsevaluating a bareselfat import time under Node)Minor rather than patch, since #118 changes how that route renders and #117 changes the query layer's failure behaviour.
Notes
npm installon a bump can quietly pull newer versions within existing ranges.versionfrompackage.json(src/components/ui/version-badge.tsx), so it picks this up with no code change — it will read0.4.0once deployed.Verification
npm run check✅ ·npm test5/5 ✅ ·npx tsc --noEmit✅ ·npm run build✅Heads-up on production
Production is still serving the 500 on
/request/<id>. Staging auto-deployed on merge and is verified returning 200, but production deploys only on a published release — so the three merged fixes are not live onscan.request.networkyet. This bump is presumably the version you'd cut that release at; the release itself is a human action and I have not taken it.