chore: release v1.0.6

Fix version generation in CI/CD builds

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.gitignore

@@ -13,11 +13,12 @@ pubspec.lock
 *.gr.dart
 *.mocks.dart
 
-# Keep version.g.dart - it's generated but should be committed
+# All generated *.g.dart files (from json_serializable, riverpod, version_builder)
-# so CI/CD builds have version info without running the generator
+# These are regenerated by build_runner during CI/CD builds
-# Other *.g.dart files (from json_serializable, etc.) are ignored
 lib/**/*.g.dart
-!lib/version.g.dart
+
+# Generated health.json (regenerated by tool/generate_health_json.dart during build)
+web/health.json
 
 # IDE
 .idea/

CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.0.6] - 2026-01-04
+
+### Fixed
+- Fixed version generation in CI/CD builds
+- Removed generated files (version.g.dart, health.json) from git tracking
+- These files are now regenerated from pubspec.yaml during Docker build
+
 ## [1.0.5] - 2026-01-04
 
 ### Changed

lib/main.dart

@@ -14,9 +14,5 @@ void main() {
     name: 'tatlock_ui',
   );
 
-  runApp(
+  runApp(const ProviderScope(child: TatlockApp()));
-    const ProviderScope(
-      child: TatlockApp(),
-    ),
-  );
 }

lib/version.g.dart

@@ -1,13 +0,0 @@
-// GENERATED FILE - DO NOT EDIT
-// Generated by build_runner from pubspec.yaml
-
-/// Application version information from pubspec.yaml
-class AppVersion {
-  AppVersion._();
-
-  static const String name = 'tatlock_ui';
-  static const String description = 'Tatlock - a Home Lab AI';
-  static const String version = '1.0.4';
-  static const int buildNumber = 1;
-  static const String fullVersion = '1.0.4+1';
-}

pubspec.yaml

@@ -16,7 +16,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
 # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
 # In Windows, build-name is used as the major, minor, and patch parts
 # of the product and file versions while build-number is used as the build suffix.
-version: 1.0.5+1
+version: 1.0.6+1
 
 environment:
   sdk: ^3.10.4

web/health.json

@@ -1,8 +0,0 @@
-{
-  "status": "healthy",
-  "name": "tatlock_ui",
-  "title": "Tatlock - a Home Lab AI",
-  "version": "1.0.4",
-  "buildNumber": 1,
-  "fullVersion": "1.0.4+1"
-}