chore(main): release 0.0.4 - #461
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d3d8bbae3e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1 +1 @@ | |||
| 0.0.3 | |||
| 0.0.4 | |||
There was a problem hiding this comment.
Keep the SPA build version in sync
This bumps the published release version to 0.0.4, but web/.env.production in the same tree still says VITE_APP_VERSION=0.0.3 (and release-please-config.json lists it as an extra-files target). Production Vite builds read that env var for the sidebar and error reports, so the v0.0.4 image would still present/report itself as 0.0.3 unless the env file is updated with the release.
Useful? React with 👍 / 👎.
c1e9f87 to
00acc11
Compare
release-please's generic updater only matches a semver pattern on the same line as the x-release-please-version marker, not the line below it. #459 placed the marker above the value, so it silently never matched — v0.0.4 (#461) bumped version.txt but left web/.env.production at 0.0.3, caught by review. Move the marker to a trailing comment on the value's own line. dotenv (Vite's env loader) strips inline # comments on unquoted values, so the runtime value stays clean — verified via a real npm run build and a grep of the bundled output. Fixes #458 Co-authored-by: mforce <>
00acc11 to
1e27bd7
Compare
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
0.0.4 (2026-08-13)
Features
Bug fixes
Refactoring
Documentation
This PR was generated with Release Please. See documentation.