Repository navigation
fix(examples): pin the release version instead of latest - #388
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 16 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
biggest-littlest
left a comment
There was a problem hiding this comment.
Examples pin the release version, enforced by the release contract with self-test mutations. 14 required checks green on b48bb44. CodeRabbit was out of free reviews; no outside review on this one.
ALARGECOMPANY
left a comment
There was a problem hiding this comment.
Examples pin the release version, enforced by the release contract with self-test mutations. 14 required checks green on b48bb44. CodeRabbit was out of free reviews; no outside review on this one.
Six of the seven example files used
ghcr.io/codeswhat/portwing:latest, so an example copied today would change behaviour under you at the next release. They now pin the release version, the same way the observability example already did.0.9.25.latestfor the Portwing image. The self-test mutates each file both ways.RELEASING.mdlists the examples among the files the release prep bumps.All five Compose examples still pass
docker compose config -q. The Kubernetes manifests keepimagePullPolicy: Always.