Tags: HagiCode-org/releases
Tags
feat(docker): add EULA acceptance gate to container startup Add mandatory EULA acceptance check before container startup. The entrypoint now validates that ACCEPT_EULA is set to an accepted opt-in value (Y, YES, TRUE, or 1) and fails fast with a clear error message when the opt-in is missing or invalid. This change implements the shared Builder EULA toggle contract: enabling the toggle exports ACCEPT_EULA=Y, and leaving it disabled omits the variable entirely. Changes: - Add validate_accept_eula() function to docker-entrypoint.sh - Gate container startup behind accepted EULA value - Update documentation to describe ACCEPT_EULA variable and behavior - Add integration tests for EULA validation logic - Add RunBashScript helper for testing shell script functions - Update verification steps in ENVIRONMENT_VARIABLES.md Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
test(docker): add tests for code-server runtime integration Add test coverage for the bundled code-server runtime implementation, ensuring the Docker build, entrypoint bootstrap, and documentation are properly aligned across all release artifacts. New test assertions: - Verify PINNED_CODE_SERVER_VERSION=4.115.0 in Dockerfile - Assert code-server npm install and version verification steps - Check configure_code_server_runtime_if_needed() in entrypoint - Validate CODE_SERVER_PASSWORD and CODE_SERVER_HASHED_PASSWORD bridging - Confirm password auth failure message when secret is missing - Verify code-server --version check during entrypoint bootstrap - Assert Code Server documentation in README and README_cn - Check Code Server Deployment Contract section in ENVIRONMENT_VARIABLES.md - Verify /app/data/code-server data directory documentation These tests ensure the container contract changes are properly implemented and documented across all release artifacts. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
test(docker): add tests for code-server runtime integration Add test coverage for the bundled code-server runtime implementation, ensuring the Docker build, entrypoint bootstrap, and documentation are properly aligned across all release artifacts. New test assertions: - Verify PINNED_CODE_SERVER_VERSION=4.115.0 in Dockerfile - Assert code-server npm install and version verification steps - Check configure_code_server_runtime_if_needed() in entrypoint - Validate CODE_SERVER_PASSWORD and CODE_SERVER_HASHED_PASSWORD bridging - Confirm password auth failure message when secret is missing - Verify code-server --version check during entrypoint bootstrap - Assert Code Server documentation in README and README_cn - Check Code Server Deployment Contract section in ENVIRONMENT_VARIABLES.md - Verify /app/data/code-server data directory documentation These tests ensure the container contract changes are properly implemented and documented across all release artifacts. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
test(docker): add tests for debian base, NVM installation, and SSH bo… …otstrap Add test coverage for the new container foundation and SSH bootstrap flow: - Verify debian:bookworm-slim base instead of node:24 - Assert NVM installation and symlink configuration - Validate PATH includes /usr/local/nvm/current/bin - Check primary CLI baseline installation patterns - Test SSH bootstrap functions and environment variable handling - Verify documentation alignment across English and Chinese docs - Confirm usermod/groupmod replaces deluser in entrypoint These tests ensure the container contract changes are properly implemented and documented across all release artifacts. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
test(docker): add tests for debian base, NVM installation, and SSH bo… …otstrap Add test coverage for the new container foundation and SSH bootstrap flow: - Verify debian:bookworm-slim base instead of node:24 - Assert NVM installation and symlink configuration - Validate PATH includes /usr/local/nvm/current/bin - Check primary CLI baseline installation patterns - Test SSH bootstrap functions and environment variable handling - Verify documentation alignment across English and Chinese docs - Confirm usermod/groupmod replaces deluser in entrypoint These tests ensure the container contract changes are properly implemented and documented across all release artifacts. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
refactor(version-monitor): simplify to only sync latest version Simplify the version monitor logic to only consider the latest Azure version for release synchronization, ignoring any historical version gaps. Changes: - Modify ReleaseVersionMonitorPlanner to check only the latest version - Update log messages to clarify historical gaps are ignored - Add test for ignoring historical gaps when latest is published - Update and rename existing tests for clarity This change ensures the monitor focuses on syncing the current latest version rather than attempting to fill in missing historical versions. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
refactor(version-monitor): simplify to only sync latest version Simplify the version monitor logic to only consider the latest Azure version for release synchronization, ignoring any historical version gaps. Changes: - Modify ReleaseVersionMonitorPlanner to check only the latest version - Update log messages to clarify historical gaps are ignored - Add test for ignoring historical gaps when latest is published - Update and rename existing tests for clarity This change ensures the monitor focuses on syncing the current latest version rather than attempting to fill in missing historical versions. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
refactor(version-monitor): simplify to only sync latest version Simplify the version monitor logic to only consider the latest Azure version for release synchronization, ignoring any historical version gaps. Changes: - Modify ReleaseVersionMonitorPlanner to check only the latest version - Update log messages to clarify historical gaps are ignored - Add test for ignoring historical gaps when latest is published - Update and rename existing tests for clarity This change ensures the monitor focuses on syncing the current latest version rather than attempting to fill in missing historical versions. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
refactor(version-monitor): simplify to only sync latest version Simplify the version monitor logic to only consider the latest Azure version for release synchronization, ignoring any historical version gaps. Changes: - Modify ReleaseVersionMonitorPlanner to check only the latest version - Update log messages to clarify historical gaps are ignored - Add test for ignoring historical gaps when latest is published - Update and rename existing tests for clarity This change ensures the monitor focuses on syncing the current latest version rather than attempting to fill in missing historical versions. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
refactor(version-monitor): simplify to only sync latest version Simplify the version monitor logic to only consider the latest Azure version for release synchronization, ignoring any historical version gaps. Changes: - Modify ReleaseVersionMonitorPlanner to check only the latest version - Update log messages to clarify historical gaps are ignored - Add test for ignoring historical gaps when latest is published - Update and rename existing tests for clarity This change ensures the monitor focuses on syncing the current latest version rather than attempting to fill in missing historical versions. Co-Authored-By: Hagicode <[email protected]> Signed-off-by: newbe36524 <[email protected]>
PreviousNext