Yuneng Jiang b5823d5894 feat(terraform): sync provider 0.3.0 from mirror and cut 0.4.0 ... The provider's release gate in project-releaser publishes only when the topmost released heading in terraform/provider/CHANGELOG.md moves past the tag the mirror already carries. That heading has been 0.2.2 since 2026-05-13, so every stable release since has correctly decided there was nothing to publish and the registry has gone stale. Two things were blocking a release: 1. The mirror shipped 0.3.0 out-of-band on 2026-07-13 (pricing_base_model, BerriAI/terraform-provider-litellm#47) after the source move, so that code exists only in the mirror. The publish rsyncs monorepo -> mirror with --delete, so publishing without this port would have deleted a released feature from the registry. 2. Nothing here declared a new version. Port #47 verbatim (resource_model.go and resource_model_crud.go are now byte-identical to the mirror's released files), backfill the 0.3.0 changelog entry it shipped under, and cut 0.4.0 covering the changes made here since the source move. 0.3.0 is not reusable as the next version -- the mirror holds that tag and the publish workflow's tag guard rejects it.		2026-08-06 09:49:13 -07:00
..
litellm	fix(docker): honor USE_DDTRACE in the componentized gateway and backend images (#35490)	2026-08-01 14:12:59 -07:00
provider	feat(terraform): sync provider 0.3.0 from mirror and cut 0.4.0	2026-08-06 09:49:13 -07:00