Merge branch 'main' into json-schemas

Signed-off-by: Charles-Edouard Brétéché <[email protected]>
kyverno · Oct 28, 2023 · 7f9ccb4 · 7f9ccb4
2 parents fa46585 + 846a8e2
commit 7f9ccb4
Show file tree

Hide file tree

Showing 4 changed files with 2 additions and 2 deletions.
diff --git a/release-notes/_template.md → .release-notes/_template.md b/release-notes/_template.md → .release-notes/_template.md
diff --git a/release-notes/main.md → .release-notes/main.md b/release-notes/main.md → .release-notes/main.md
diff --git a/release-notes/v0.0.1.md → .release-notes/v0.0.1.md b/release-notes/v0.0.1.md → .release-notes/v0.0.1.md
diff --git a/docs/dev/release/README.md b/docs/dev/release/README.md
@@ -18,8 +18,8 @@ git push origin $TAG
 
 ## Release notes
 
-Release notes for the `main` branch lives in [main.md](../../release-notes/main.md).
+Release notes for the `main` branch lives in [main.md](../../.release-notes/main.md).
 
 Make sure it is up to date and rename the file to the version being released.
 
-You can then copy [_template.md](../../release-notes/_template.md) to [main.md](../../release-notes/main.md) for the next release.
+You can then copy [_template.md](../../.release-notes/_template.md) to [main.md](../../.release-notes/main.md) for the next release.