fix: default Compose deployments to the public edge image - #13
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🧰 Additional context used📓 Path-based instructions (2)compose/**⚙️ CodeRabbit configuration file
Files:
**/*.md⚙️ CodeRabbit configuration file
Files:
🔇 Additional comments (4)
Summary by CodeRabbit
WalkthroughThe default Codex container image is changed from the stable tag to ChangesEdge image defaults
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
stabletag toedge-amd64.edge-amd64..env.examplewith the same public experimental image.CHANGELOG.md.Why
The repository has no stable release yet. A fresh deployment using the current defaults would try to pull a tag that is not published, while the documented and available testing channel is
edge-amd64.Impact
Fresh generic Docker and TrueNAS deployments now follow the public AMD64 development channel by default. The image remains explicitly experimental and mutable; tested deployments should still record and pin the published digest.
Validation
make validate