You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suppose a scenario where we release a 1.0.0, and we introduce a backwards incompatible change on top of that. We have not yet released yet, so the version number would still be 0.0.5, yet a breaking change occurred. If a user runs the recommended
then they will get a backwards incompatible change.
Instead, we should find a way to install a specific version of the yamldifftool as a helm plugin. This may require introducing git tags, or github releases.
Expected behavior:
Actual behavior:
How to reproduce:
Logs:
Environment:
OS:
OS Version:
Distribution:
Python version:
The text was updated successfully, but these errors were encountered:
Describe the issue:
Suppose a scenario where we release a 1.0.0, and we introduce a backwards incompatible change on top of that. We have not yet released yet, so the version number would still be 0.0.5, yet a breaking change occurred. If a user runs the recommended
then they will get a backwards incompatible change.
Instead, we should find a way to install a specific version of the yamldifftool as a helm plugin. This may require introducing git tags, or github releases.
Expected behavior:
Actual behavior:
How to reproduce:
Logs:
Environment:
The text was updated successfully, but these errors were encountered: