fix(ci): publish Docker images for prereleases @osterman (#2792)
## what- Publish the existing multi-architecture Atmos Docker image for both stable and prerelease GitHub releases.
- Keep Docker image publishing disabled for manual workflow dispatches.
why
- Native CI users consume Atmos through Docker images and need prerelease tags to test upcoming releases.
- Homebrew remains stable-release-only.
references
- N/A
Summary by CodeRabbit
- Chores
- Updated release automation so the Docker build job runs for release events.
🚀 Enhancements
Add deprecation validation warnings @osterman (#2793)
## what- Keep supported legacy Atmos configuration valid while emitting schema-driven deprecation warnings in CLI validation and the LSP.
- Restore legacy Terraform dependency compatibility and add a customer regression scenario.
why
- Prevent 1.224 schema validation from blocking existing customer configuration while providing actionable migrations.
references
- N/A
Summary by CodeRabbit
- New Features
- Added deprecated-field warnings (with replacement guidance and file/line/column locations) to config validation, stack validation, schema validation, and language-server diagnostics.
- Updated schemas to mark legacy and dependency-related fields as deprecated, including
depends_onreplacement guidance. - Restored backward-compatible
depends_onhandling for legacy manifest layouts.
- Bug Fixes
- Schema validation now succeeds when there are no schema errors, even if warnings are present.
- Deprecation scanning is best-effort: failures no longer abort validation.
- Tests
- Added fixtures and unit/CLI tests covering deprecated-field compatibility and dependency fallback behavior.
- Documentation
- Documented deprecation warnings behavior across CLI and LSP.
fix(yaml): decode JSON after whitespace-trimmed function tags @osterman (#2780)
## what- Accept
[and{as valid boundaries after YAML function tags. - Add end-to-end coverage for whitespace-trimmed
!templatelist and map output. - Add a durable fix record under
docs/fixes.
why
- Go-template whitespace trimming can render
!template[...]or!template{...}, which strict tag matching left as literal strings.
references
- Closes #2778
Summary by CodeRabbit
- Bug Fixes
- Fixed YAML
!templateparsing so whitespace-trimmed templates that render JSON arrays/objects decode correctly. - Improved
!templateboundary handling around whitespace, JSON delimiters, end-of-input, and zero-argument tags, preventing accidental literal-string output.
- Fixed YAML
- Documentation
- Added a fix record documenting the corrected parsing behavior and edge cases.
- Tests
- Extended fixtures and added unit/integration assertions for trimmed list/map outputs and near-miss tag names.