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.
> 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://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/" rel="nofollow">https://grafana.com/blog/2021/04/20/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.