chore(production): chart 2.3.0, which pins the IDE images to EduIDE 1.3.0 - #142
Conversation
….3.0 Bonn, Mannheim and TUM production move to chart 2.3.0, whose appVersion is 1.3.0, so every IDE image lands on the tags that release published. Mannheim's versions.ide pin goes with it. It named pr-170 because thm-java-25 was an unmerged pull request and no numbered release published it; #170 merged and 1.3.0 is the first release that does, which is exactly the condition the comment named for dropping it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
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 |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Publish chart 2.3.0 and all 1.3.0 images, and update validation to test the production chart pins.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (3)
What changed in this PR
Updates all production environments to chart 2.3.0, which uses EduIDE 1.3.0.
Changes:
- Bumps chart versions for Bonn, Mannheim, and TUM production.
- Removes Mannheim’s temporary
pr-170image override. - Updates Mannheim’s related comments.
| File | Summary |
|---|---|
environments/mannheim.eduide.aet.cit.tum.de/values.yaml |
Removes the temporary IDE tag override. |
environments/mannheim.eduide.aet.cit.tum.de/env.yaml |
Bumps Mannheim to chart 2.3.0; CI does not validate this production pin. |
environments/eduide.artemis.cit.tum.de/env.yaml |
Bumps TUM production to 2.3.0; chart and image artifacts are not yet available, and CI coverage is incomplete. |
environments/bonn.eduide.aet.cit.tum.de/env.yaml |
Bumps Bonn to chart 2.3.0; CI does not validate this production pin. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| namespace: eduide-tum-production | ||
| platform: | ||
| chartVersion: 2.2.1 | ||
| chartVersion: 2.3.0 |
There was a problem hiding this comment.
Half of this is now resolved: EduIDE's v1.3.0 release build finished successfully and all 13 image tags are published (verified each with docker manifest inspect). Chart 2.3.0 is still pending EduIDE-Helm#43.
The ordering stands as described - Helm#43, then #141 (staging), then this. #143 makes CI enforce the chart half rather than leaving it to the description.
Moves all three production installations from chart 2.2.1 to 2.3.0:
eduide.artemis.cit.tum.debonn.eduide.aet.cit.tum.demannheim.eduide.aet.cit.tum.deChart 2.3.0 carries
appVersion: 1.3.0, so every IDE image renders on the tags EduIDE v1.3.0 published. Merging this is the production deploy.Mannheim's pin goes too
versions.ide: pr-170named an unmerged pull request, becausethm-java-25had no numbered tag. EduIDE#170 merged and 1.3.0 is the first release to publish it, which is the exact condition the comment gave for dropping the block. Mannheim now rendersghcr.io/eduide/eduide/thm-java-25:1.3.0from the chart like every other installation.What else rides along
Production was on 2.2.1, so this is one minor: 2.2.x → 2.3.0. The only chart change between them is the version and appVersion bump itself.
Depends on
ImagePullBackOff.Verification
./scripts/test-deploy-logic.shagainst the 2.3.0 chart: ALL PASS, including the production assertions (shared cache off in all three, storage class from the cluster, hostnames match).Rendered image tags with that chart:
eduide.artemis.cit.tum.de→ 8 images, all:1.3.0bonn→javascript:1.3.0mannheim→thm-java-25:1.3.0Note for whoever bootstraps next
eduide-clusteralso went to 2.3.0 in EduIDE-Helm#43 - it is kept at the same version aseduideby hand. It is aBootstrap clusterworkflow input rather than a value in a file, so nothing here bumps it; pass 2.3.0 the next time that workflow runs.🤖 Generated with Claude Code