Releases: wolfgangbures/HA_GITUpdate
Releases · wolfgangbures/HA_GITUpdate
v0.7.5
Bug Fixes
- Fix error events firing to wrong HA endpoint; deployment and validation failures now correctly fire
git_update.files_changed.errorinstead ofgit_update.files_changed. - Fix
api.pyindentation corruption and hardcoded version; version is now read dynamically fromconfig.json.
v0.7.5-beta
Bug Fixes
- Fix error events firing to wrong HA endpoint; deployment and validation failures now correctly fire
git_update.files_changed.errorinstead ofgit_update.files_changed. - Fix
api.pyindentation corruption and hardcoded version; version is now read dynamically fromconfig.json.
v0.8.0-beta
Beta Release v0.8.0-beta
- New: Full-Sync command and API endpoint (/full-sync) to force update all repo files into the config directory without deleting extras
- Lovelace YAML example for UI button to trigger full-sync
- Documentation updates for full-sync usage and UI integration
- Bugfixes and improvements for disaster recovery scenarios
Please test and report any issues before stable release!
v0.7.4
Changes
- Fixed YAML validation to handle Home Assistant custom tags (e.g., !include)
- configuration.yaml now deploys correctly even with custom YAML syntax
- Improved error handling for custom tag detection
- Updated version strings in application code
Bug Fixes
- Resolved issue where configuration.yaml with !include directives would fail validation and skip deployment
- Files with custom YAML tags are now allowed through with a warning, while standard YAML errors are still caught
v0.7.4-beta
Beta Release
Changes
- Fixed YAML validation to handle Home Assistant custom tags (e.g., !include)
- configuration.yaml now deploys correctly even with custom YAML syntax
- Improved error handling for custom tag detection
- Updated version strings in application code (main.py, api.py)
What to test
- Deploy configuration.yaml with !include directives
- Verify other YAML files with custom tags deploy properly
- Confirm standard YAML syntax errors are still caught and reported
- Check that version 0.7.4 is reported in logs and API responses
Please test this beta before approving for stable release.
v0.7.3
Fix credential environment propagation in git operations
Changes
- Pass environment variables directly to clone_from() and Remote.fetch() methods
- The custom_environment context manager was not properly propagating credentials to these operations
- Add newline terminator and flush to git_askpass.py credential helper (from v0.7.2)
- Fully resolves authentication failures in non-interactive container environments
Upgrade Notes
This release fixes the 'fatal: could not read Username for https://github.com: No such device or address' error that prevented initial repository clones in containerized environments.
v0.7.3-beta
BETA RELEASE - Please test before upgrading production systems
Fix credential environment propagation in git operations
Changes
- Pass environment variables directly to clone_from() and Remote.fetch() methods
- The custom_environment context manager was not properly propagating credentials to these operations
- Combined with v0.7.2, this fully resolves authentication failures in non-interactive container environments
Testing
Please test this beta in your environment and report any issues before the stable release.
v0.7.2
Fix git credential helper for non-interactive environments
Changes
- Add newline terminator to git askpass helper output
- Add explicit stdout flushing to ensure proper credential delivery
- Resolves 'fatal: could not read Username for https://github.com: No such device or address' errors in containerized environments
Fix for authentication issues
What's Changed
- fix: non-interactive git HTTPS auth + redact secrets by @wolfgangbures in #5
- fix: bundle git askpass helper by @wolfgangbures in #6
- chore: bump to 0.7.1 + askpass preflight by @wolfgangbures in #7
New Contributors
- @wolfgangbures made their first contribution in #5
Full Changelog: v0.7...v0.71
Fix Config descriptions
Full Changelog: v0.61...v0.7