Add missing .VERSION file

[adamoutler]

Missing file

Summary by CodeRabbit

• Chores
  • Added version indicator file for internal development tracking.

[coderabbitai]

Walkthrough

A new .VERSION file has been added to the repository containing "Development" as a version indicator placeholder. No code or logic changes are introduced.

Changes

Cohort / File(s)	Change Summary
Version Configuration \.VERSION	Added version indicator placeholder file with "Development" content

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This change introduces a single, static configuration file with minimal content and no logic or structural implications.

Poem

🐰 A .VERSION file hops into place,
Marking "Development" with grace,
Simple, small, and oh-so-neat,
A placeholder makes the setup complete! 🌱

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add missing .VERSION file' clearly and specifically describes the main change—adding a .VERSION file to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4f47dbf and 734db42.

📒 Files selected for processing (1)

• .VERSION (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: docker_dev

🔇 Additional comments (1)

.VERSION (1)

1-1: Let me search for the getBuildTimeStampAndVersion function:Based on my comprehensive investigation, I now have sufficient evidence to provide the rewritten review comment. The .VERSION file is clearly being actively used in the application for tracking application versions and detecting upgrades.

---

Verify the .VERSION file content and ensure build automation updates it appropriately.

The .VERSION file is actively used in the application:

• The application reads the file in front/php/templates/version.php and references /app/.VERSION
• The server/initialise.py file reads the version to detect application upgrades (line 680 compares previous version against new version)
• The Dockerfile copies .VERSION into the container at runtime

Action items before merge:

1. Confirm that "Development" is the intended placeholder for development/non-release builds
2. Verify your CI/CD pipeline or build process updates .VERSION with actual version numbers (e.g., from git tags or release identifiers) for production deployments
3. Ensure the version comparison logic in server/initialise.py (line 680) works correctly with your versioning scheme

The application will use "Development" as the version indicator if no build process updates this file, which may cause spurious upgrade notifications in development environments.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Remove trailing whitespace from version string.

Line 1 contains a trailing space after "Development" which should be removed for consistency and to avoid potential parsing issues when this file is read by scripts or tools.

Apply this diff:

-Development 
+Development

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Development
	Development

🤖 Prompt for AI Agents

.VERSION lines 1-1: the version string contains a trailing space ("Development
"). Remove the trailing whitespace so the line is exactly "Development" with no
leading or trailing spaces; save the file ensuring no extra newline characters
beyond a single newline at EOF if your project expects it.