Version bump to 1.0.11 and 1.0.r11

- Update version numbers across all files (main.py, __init__.py, settings.py, build.py, web_dashboard)
- Add comprehensive changelog entry for 1.0.11 documenting the venue timezone system implementation
- Document the fix for UTC midnight day change issues and venue timezone configuration
parent 2661425a
......@@ -2,6 +2,34 @@
All notable changes to this project will be documented in this file.
## [1.0.11] - 2026-01-20
### Added
- **Venue Timezone System**: Complete timezone-aware system to fix UTC midnight day change issues
- **System Timezone Auto-Detection**: Automatic detection of system timezone with proper IANA mapping
- **Venue Timezone Configuration**: Configurable venue timezone with system timezone as default fallback
- **Timezone Utility Functions**: Comprehensive timezone conversion utilities (`timezone_utils.py`)
- **Database Timezone Storage**: Venue timezone stored in configuration database with persistence
### Fixed
- **Critical**: Day change calculations now use venue local time instead of UTC, fixing fixture day appartenence issues
- **UTC Midnight Problem**: Resolved incorrect day boundaries where UTC midnight didn't correspond to venue local midnight
- **Fixture Association**: Matches and bets now correctly associated with venue days regardless of UTC offset
- **Timezone Mapping**: Added SAST (South Africa Standard Time) to IANA timezone mapping
### Enhanced
- **Games Thread**: All date filtering operations now respect venue timezone for accurate day calculations
- **Web Dashboard API**: Reports, bets, and matches filtered by venue timezone with proper date handling
- **Configuration UI**: Venue timezone configurable through web dashboard with validation
- **Cross-Platform Compatibility**: Timezone system works consistently across all supported platforms
### Technical Details
- **Timezone Architecture**: Implemented venue timezone system with auto-detection and configuration override
- **Database Integration**: Venue timezone stored in configuration table with proper initialization
- **API Enhancement**: All date-based API endpoints now use venue timezone for filtering and calculations
- **Backward Compatibility**: Existing UTC data remains intact while new operations use venue timezone
- **Fallback Strategy**: System timezone → Environment variable (VENUE_TIMEZONE) → UTC ultimate fallback
## [1.2.11] - 2025-08-28
### Fixed
......
......@@ -14,7 +14,7 @@ from typing import List, Dict, Any
# Build configuration
BUILD_CONFIG = {
'app_name': 'MbetterClient',
'app_version': '1.0.10',
'app_version': '1.0.11',
'description': 'Cross-platform multimedia client application',
'author': 'MBetter Team',
'entry_point': 'main.py',
......
......@@ -205,7 +205,7 @@ Examples:
parser.add_argument(
'--version',
action='version',
version='MbetterClient 1.0.10'
version='MbetterClient 1.0.11'
)
# Timer options
......
......@@ -4,7 +4,7 @@ MbetterClient - Cross-platform multimedia client application
A multi-threaded application with video playback, web dashboard, and REST API integration.
"""
__version__ = "1.0.10"
__version__ = "1.0.11"
__author__ = "MBetter Project"
__email__ = "dev@mbetter.net"
__description__ = "Cross-platform multimedia client with video overlay and web dashboard"
......
......@@ -366,7 +366,7 @@ class AppSettings:
timer: TimerConfig = field(default_factory=TimerConfig)
# Application settings
version: str = "1.0.10"
version: str = "1.0.11"
debug_mode: bool = False
dev_message: bool = False # Enable debug mode showing only message bus messages
debug_messages: bool = False # Show all messages passing through the message bus on screen
......
......@@ -209,7 +209,7 @@ class WebDashboard(ThreadedComponent):
def inject_globals():
return {
'app_name': 'MbetterClient',
'app_version': '1.0.10',
'app_version': '1.0.11',
'current_time': time.time(),
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment