Skip to content

Prevent runtime environment from overriding release version - #86

Merged
emnl51 merged 5 commits into
mainfrom
codex/verify-deployed-version
Sep 4, 2026
Merged

emnl51 merged 5 commits into
mainfrom
codex/verify-deployed-version

Conversation

@emnl51

@emnl51 emnl51 commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • bake the release into BERT_BUILD_VERSION
  • prefer the baked value over legacy runtime APP_VERSION
  • document that APP_VERSION must not be stored in .env
  • cover stale runtime override behavior with a regression test

Why

The server's .env contained APP_VERSION=19.1.3, which overrode the freshly built 20.1.1 image at container startup.

Validation

  • 237 passed
  • release and updater static checks passed

@emnl51
emnl51 merged commit 2fdddf6 into main Sep 4, 2026
7 of 8 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d9145e0241

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
Comment on lines +100 to +102
Do not set `APP_VERSION` in `.env`. Release versions are embedded into the
container image at build time; a runtime override can otherwise make the UI
report a stale version.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve a version source for local Compose builds

When a source-deployment user follows this new instruction and removes APP_VERSION, the documented docker compose up -d --build path still does not pass an APP_VERSION build argument (docker-compose.yml only specifies build: .). Consequently BERT_BUILD_VERSION is baked as empty and app/version.py falls back to the outdated DEFAULT_VERSION (17.2.2), so fresh source deployments continue reporting the wrong version and reuse the wrong UI cache key. Either inject the actual version for this build path or scope this instruction to prebuilt images.

Useful? React with 👍 / 👎.

Comment thread README.md
@@ -152,24 +156,6 @@ After signing in as the administrator:
4. Configure personal Telegram or email notifications in the user workspace.
5. Configure account-activation email under **Administration → System Email**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the profile-configuration documentation

This version-focused change also removes the recently added explanation of Profile essentials, role-level eligibility, strict working-time behavior, and linked-profile deletion constraints. Administrators consulting the initial-configuration section now lose the detailed guidance needed to understand these non-obvious behaviors; this unrelated deletion should be reverted unless those instructions are deliberately relocated elsewhere.

Useful? React with 👍 / 👎.

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.

1 participant