Skip to content

chore: bump version to 0.4.0 - #119

Merged
rodrigopavezi merged 1 commit into
mainfrom
chore/bump-version-0.4.0
Jul 30, 2026
Merged

chore: bump version to 0.4.0#119
rodrigopavezi merged 1 commit into
mainfrom
chore/bump-version-0.4.0

Conversation

@rodrigopavezi

Copy link
Copy Markdown
Contributor

Bumps the version 0.3.40.4.0 and regenerates the lockfile.

Covers the three fixes just merged:

Minor rather than patch, since #118 changes how that route renders and #117 changes the query layer's failure behaviour.

Notes

  • The lockfile diff is only the two version fields — no dependency was upgraded as a side effect. Worth stating, since running npm install on a bump can quietly pull newer versions within existing ranges.
  • The footer version badge reads version from package.json (src/components/ui/version-badge.tsx), so it picks this up with no code change — it will read 0.4.0 once deployed.

Verification

npm run check ✅ · npm test 5/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 on scan.request.network yet. 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.

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-apps

greptile-apps Bot commented Jul 29, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the application release metadata from version 0.3.4 to 0.4.0.

  • Keeps the root package version synchronized between package.json and package-lock.json.
  • Leaves all resolved dependency versions and integrity data unchanged.

Confidence Score: 5/5

The 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

Filename Overview
package.json Updates the application version from 0.3.4 to 0.4.0 without changing scripts or dependencies.
package-lock.json Synchronizes both root-package version fields to 0.4.0 without changing resolved dependencies.

Reviews (1): Last reviewed commit: "chore: bump version to 0.4.0" | Re-trigger Greptile

rodrigopavezi commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Merge activity

  • Jul 30, 5:07 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jul 30, 5:08 PM UTC: @rodrigopavezi merged this pull request with Graphite.

@rodrigopavezi
rodrigopavezi merged commit 18b6aa8 into main Jul 30, 2026
9 checks passed
@rodrigopavezi
rodrigopavezi deleted the chore/bump-version-0.4.0 branch July 30, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants