v2.6.48
Pre-release bot rollout can be set per team
- 3improved
- 2fixed
This release changes how the pre-release bot build is rolled out to teams. It matters to self-hosted operators who use the rollout settings to send part of their traffic to the pre-release build. Requests, responses and webhooks of the public API are unchanged.
Improvements
- A team assigned to the pre-release build now carries its own share: at 100% all of that team's bots run the pre-release build, at 10% about one in ten do. The team's share applies whatever the global share is set to.
- A global share of 0 now switches off only the global share. Team assignments keep applying; to roll everything back, clear the assignments and set the global share to 0.
- The rollout settings return each assigned team with its name, and how many of the eligible teams the global share currently selects, so the effect of a setting can be checked before relying on it.
Bug Fixes
- Assigning one team while the global share was set to 100% moved every team to the pre-release build instead of only the assigned team. A team assignment now affects that team alone.
- Unknown or repeated team IDs in the rollout assignments are rejected instead of being saved.