Skip to content

Wealth Watcher v0.3.0

Choose a tag to compare

@paevans87 paevans87 released this 14 Aug 11:16
· 84 commits to main since this release
c8dbbf7

Wealth Watcher v0.3.0

Highlights

  • Makes the browser-only public demo banner visibly opaque, consistently positioned, and available with clear links to the main site and demo reset action.
  • Improves the app bar's contrast and layering so navigation remains readable over the application and demo layouts.
  • Adds a build-time demo-mode switch for the Pages demo while keeping the banner hidden in normal application builds.
  • Publishes tagged stable images with the moving latest alias so deployments can follow the latest successful release.

Fixes

  • Prevents the demo banner and app bar from becoming transparent or allowing application content to show through them.
  • Improves mobile containment for high-data pages and budget controls, reducing horizontal overflow and narrow-screen layout failures.
  • Adds regression coverage for the responsive shell, demo banner, app bar, and mobile layout contracts.

Upgrade notes

  • No application API or database migration changes are included.
  • No configuration change is required for self-hosted application builds. The public Pages demo enables VITE_DEMO_MODE and VITE_BASE_PATH in its existing workflow.
  • Back up PostgreSQL and the ASP.NET Data Protection key directory before upgrading as a normal operational precaution.
  • Tagged API and web images are rebuilt by the release workflow. Use the v0.3.0 tags or immutable digests for reproducible deployments; use latest when following the latest successful stable release.

Docker images

  • ghcr.io/paevans87/wealth-watcher-public-api:v0.3.0
  • ghcr.io/paevans87/wealth-watcher-public-web:v0.3.0
  • The successful tagged workflow also moves the stable latest alias for both images.
  • Image digests should be recorded from the completed tagged workflow when a deployment requires immutable release evidence.

Known issues

  • Forecast views are currently unreliable and may not behave or calculate as expected. Improvements are planned.
  • The browser-only public demo uses fictional, resettable data and does not connect to the API, database, accounts, or provider integrations.