What goodrain/rainbond shipped
Written by FoxPlug from the repository's own releases; not affiliated with Rainbond. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/goodrain/rainbond; Rainbond did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Released v6.10.3, which fixes gateway reconciliation during fresh installation so existing route and upstream IDs receive updated configuration. Release
- Added support for template artifacts and precise team quotas. Pull request #2749
- Added a release smoke workflow that tests a fresh standalone install before publishing, because v6.10.2 shipped with a standalone install whose console never comes up. Pull request #2746
- Added a release step that converts release images to eStargz before publishing, since the standalone chart pulls images that nothing in the release flow built and v6.10.1 and v6.10.2 were missed. Pull request #2745
- Added a standalone job to release-publish that builds amd64 and arm64 images from the rainbond-console release tag instead of building the image by hand after each release. Pull request #2744
- Changed the docs version table to update only the current version row and stop adding past versions, which pointed at dead links. Pull request #2739
- Changed the commit message check to check the PR title and commit subjects only, and to require the PR title to follow Conventional Commits. Pull request #2740
- Added the other release approvers as code owners so they can approve the release-go and release-publish environments. Pull request #2747
- Changed release task filing to put each release task in its vX.Y project with the release label, report the iteration's open tasks in the release report, and use the RAIN- prefix in task links. Pull request #2741
- Changed the release assistant to notify the progress group when a release is started from Feishu. Pull request #2727
Why it matters
This week's release work targets the standalone install path: v6.10.2 shipped with an install whose console never comes up, and the new smoke test, eStargz conversion and standalone image build during publish address that gap. The v6.10.3 release fixes gateway reconciliation during fresh installation so existing route and upstream IDs get updated configuration.
Changelog entry
- Release v6.10.3: fix gateway reconciliation during fresh installation so existing route and upstream IDs receive updated configuration. Release
- Support template artifacts and precise team quotas. Pull request #2749
- CI release: test a fresh standalone install before publishing. Pull request #2746
- CI release: convert release images to eStargz before publishing. Pull request #2745
- CI release: build the standalone image during release-publish for amd64 and arm64 from the rainbond-console release tag. Pull request #2744
- Docs release: stop archiving past versions in the docs version table and update only the current version row. Pull request #2739
- CI: check the PR title and commit subjects only, and require the PR title to follow Conventional Commits. Pull request #2740
- Release: add the other release approvers as code owners for the release-go and release-publish environments. Pull request #2747
- Docs release: file release tasks under the version iteration and use the RAIN- prefix in task links. Pull request #2741
- Docs release: notify the progress group from the release assistant. Pull request #2727
- Chore release: remove the agent skill moved to rainbond-multica-skills. Pull request #2742
- Sync latest main into the disk cleanup branch. Pull request #2748
V6.10.3 is out, fixing gateway reconciliation during fresh install so existing route and upstream IDs get updated config. The release flow now test-installs a fresh standalone image before publishing, converts images to eStargz, and builds standalone images during publish.
Rainbond v6.10.3 is released. It fixes gateway reconciliation during fresh installation so existing route and upstream IDs receive updated configuration. Around the release, the release flow changed to test a fresh standalone install before publishing, convert release images to eStargz before publishing, and build the standalone image during release-publish for amd64 and arm64 from the rainbond-console release tag. These steps respond to recent releases where the standalone install pointed at images that did not exist or came up without a console. The docs version table now updates only the current version row, and the commit message check now checks the PR title and commit subjects only.
Week of October 26, 2026
What shipped
- Released v6.10.2-release, which handles missing code source types by defaulting to Git and lets you set BUILD_POD_CPU and BUILD_POD_MEMORY for source build Pod resources. Release
- Released v6.10.0-release with Git OAuth reauthorization and account switching, service activation on SQLite, and a 409 instead of 500 when market app event cleanup coordination is unavailable. Release
- Released v6.10.1-release with truncated app version commit messages that avoid garbled text and stricter path validation for build source directories. Release
- Fixed recognition of ANSI-colored CNB lifecycle phase headers so real builds produce phase timing records while keeping the colored output. Pull request #2731
- Fixed CNB source package rebuilds by extracting the archive into its own temporary directory instead of reusing the previous job's modified workspace. Pull request #2732
- Fixed configuration group bindings so pending component selections are preserved before the components exist and applied only within the same application. Pull request #2733
- Fixed config group variable rendering to be isolated per component. Pull request #2729
- Split the docs pull request into its own release job so a failure there does not block verify, and added a roi job. Pull request #2734
- Fixed the release gate E2E job log download by using curl. Pull request #2730
- Merged the v6.10.2 dev branch. Pull request #2736
Why it matters
This week covers three releases: v6.10.0 adds Git OAuth reauthorization and SQLite service activation, v6.10.1 tightens version message handling and build source path checks, and v6.10.2 makes builds easier to configure with Pod CPU and memory settings. CNB builds get several fixes for colored log recognition and polluted workspaces from rebuilt source packages. Configuration group bindings now survive component creation and render variables per component.
Changelog entry
- Released v6.10.2-release: missing code source types default to Git, BUILD_POD_CPU and BUILD_POD_MEMORY configure source build Pod resources, and build worker health checks and message queue cancellation are improved. Release
- Released v6.10.0-release: Git OAuth reauthorization and bound account switching, SQLite service activation, config group binding and per-component variable rendering fixes, and a 409 for unavailable market app event cleanup coordination. Release
- Released v6.10.1-release: app version commit messages truncate safely to avoid garbled text, and build source directory paths get stronger validation. Release
- Fixed CNB lifecycle phase detection to strip ANSI color codes when matching headers while preserving the colored build output. Pull request #2731
- Fixed CNB source package rebuilds by extracting the archive into an owned temporary directory. Pull request #2732
- Fixed configuration group bindings to keep pending component selections and apply them only within the same application. Pull request #2733
- Fixed config group variable rendering to be isolated per component. Pull request #2729
- Split the docs pull request out of publish into its own job and added a roi job after release. Pull request #2734
- Fixed the release gate to download E2E job logs with curl. Pull request #2730
- Merged the v6.10.2 dev branch. Pull request #2736
Rainbond v6.10.0, v6.10.1 and v6.10.2 are out. Highlights: Git OAuth reauthorization, SQLite service activation, BUILD_POD_CPU and BUILD_POD_MEMORY for source builds, cleaner CNB build logs, and config group bindings that survive component creation.
Three Rainbond releases shipped this week. v6.10.0 adds Git OAuth reauthorization and account switching, service activation on SQLite, and a 409 response when market app event cleanup coordination is unavailable. v6.10.1 tightens build source path validation and avoids garbled text in app version commit messages. v6.10.2 handles missing code source types by defaulting to Git and lets you configure build Pod CPU and memory with BUILD_POD_CPU and BUILD_POD_MEMORY. CNB builds got fixes for colored lifecycle log recognition and workspace pollution on rebuilt source packages, and config group bindings are now preserved before components exist and rendered per component.
Week of September 14, 2026
What shipped
- Release v6.9.10-release includes UDP support for components, sudo user support in installation tooling, disk IO detection before installation, and fixes for nginx.conf overwrite, storage quota enforcement, offline plugin display, multi-architecture image selection, component naming rules, and application deletion cleanup. Release
- Gateway inbound mTLS support added for encrypted communication at the gateway entry point. Pull request #2702
- CRD deletion orchestration and PVC storage expansion capabilities implemented. Pull request #2698
- Fixed reporting of Kubernetes errors when creating TCP routes. Pull request #2703
- Custom component configuration is now preserved during upgrades. Pull request #2701
- Source builds now tolerate dedicated node taints. Pull request #2704
- README description corrected. Pull request #2700
Why it matters
This release focuses on improving installation reliability with disk IO detection and sudo support, while adding security features through gateway mTLS. Fixes address critical issues with component configuration persistence during upgrades and proper cleanup during application deletion.
Changelog entry
- Components now support UDP configuration Release
- Installation tools support sudo users Release
- Added disk IO detection before installation Release
- Fixed nginx.conf being overwritten during builds Release
- Fixed component storage quota not being enforced Release
- Fixed offline environment plugin display Release
- Fixed multi-architecture selection from image repositories Release
- Fixed component naming rules when creating from component library Release
- Fixed underlying data cleanup when deleting entire applications Release
- Added gateway inbound mTLS Pull request #2702
- Orchestrate CRD deletion and expand PVC storage Pull request #2698
- Preserve custom component configuration during upgrades Pull request #2701
- Report Kubernetes errors when creating TCP routes Pull request #2703
- Tolerate dedicated node taints in source builds Pull request #2704
Rainbond v6.9.10 is out. Gateway mTLS, UDP components, improved installation checks, and fixes for configuration preservation during upgrades.
Rainbond v6.9.10 brings enhanced security with gateway inbound mTLS, expands component capabilities with UDP support, and improves the installation experience with disk IO detection and sudo user support. The release also fixes critical issues including configuration preservation during upgrades and proper cleanup during application deletion.