CNCF: Third Party Dependencies that have been Relicensed to AGPL

If you internally build and test against the last GPL version, but everyone downstream of you uses the newest AGPL version, is that okay? I remember RMS arguing that shipping a stub readline would not be sufficient to escape readline's GPL when the CLISP developer did it, but in this case it's not a stub, it's just a differently licensed API compatible piece of software.

&gt; Recently (in early 2021), CNCF projects have discovered that some existing dependencies they use have been relicensed by their licensors from Apache-2.0 to the GNU Affero General Public License v3.0, AGPL-3.0.<p>I wonder if this new policy is in response (and the line above is referencing) <a href="https:&#x2F;&#x2F;grafana.com&#x2F;blog&#x2F;2021&#x2F;04&#x2F;20&#x2F;grafana-loki-tempo-relicensing-to-agplv3&#x2F;" rel="nofollow">https:&#x2F;&#x2F;grafana.com&#x2F;blog&#x2F;2021&#x2F;04&#x2F;20&#x2F;grafana-loki-tempo-relic...</a><p>If Grafana is going to be removed from logmon stacks, that is going to be a painful component to replace.