We aim to keep our fork of go-control-plane synchronized with the upstream repository. We’ve documented our proposed steps in a MADR, which outlines the process we plan to follow.
Implementation information
I've created a release v0.13.1-kong-1, diverging from v0.13.1, so we can use a version that includes our custom changes. The goal is to keep our tags distinct from the upstream, so I plan to remove v0.13.2 from our fork to avoid confusion.
Motivation
We aim to keep our fork of go-control-plane synchronized with the upstream repository. We’ve documented our proposed steps in a MADR, which outlines the process we plan to follow.
Implementation information
I've created a release
v0.13.1-kong-1
, diverging fromv0.13.1
, so we can use a version that includes our custom changes. The goal is to keep our tags distinct from the upstream, so I plan to removev0.13.2
from our fork to avoid confusion.Supporting documentation
https://docs.google.com/document/d/1n9hQkTubtODIJl_NThF0uvhcqXJo5OU-lU3X3N81hW4/edit?tab=t.0#heading=h.n6cmlf1eel2z
Fix #XX