David ReissandGitHub 75e012362b Gradual config rollouts (#8922) ...

## What changed?
Support gradual config rollouts by key (e.g. task queue partition).

## Why?
Rolling out changes slowly, and also mostly-synchronized across
processes.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [x] added new unit test(s)
- [ ] added new functional test(s)

## Potential risks
Time-based changes can be risky if you set something for the future and
forget about it. We should have validation that prevents changes from
being set too far in the future or outside of business hours.

2026-01-06 11:03:32 -08:00

..

task_queue_id_test.go

Remove license header from every file (#7689)

2025-05-01 18:50:21 -07:00

task_queue_id.go

Gradual config rollouts (#8922)

2026-01-06 11:03:32 -08:00

task_queue_validator_test.go

Remove a bunch of redundant utf-8 validation (#7720)

2025-05-07 20:04:42 -07:00

task_queue_validator.go

Refactor: use new serviceerror.New...f constructors (#7785)

2025-05-17 00:21:32 +00:00