Skip to content

Commit 0ce44c3

Browse files
committed
release(v0.33.0): prepare release
This is the official v0.33.0 release. Signed-off-by: Artem Chernyshev <[email protected]>
1 parent 592f916 commit 0ce44c3

File tree

2 files changed

+14
-10
lines changed

2 files changed

+14
-10
lines changed

hack/release.toml

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,23 @@ github_repo = "siderolabs/omni"
66
match_deps = "^github.com/((talos-systems|siderolabs)/[a-zA-Z0-9-]+)$"
77

88
pre_release = false
9-
previous = "v0.19.0"
9+
previous = "v0.32.0"
1010

1111
[notes]
1212

13-
[notes.kubernetes-config]
14-
title = "Kubeconfig Changes"
13+
[notes.talos-upgrades]
14+
title = "Machine Allocation Changes"
1515
description = """\
16-
Omni now generates Kubernetes configs without accessing Talos API.
17-
"""
16+
From now on Omni doesn't allow adding machines to a cluster which has lower major or minor version of Talos.
17+
Which means that adding a machine to a cluster which will lead to downgrade of Talos version is no longer possible.
18+
It is done to avoid all kinds of weird issues which Talos downgrades might lead to."""
1819

19-
[notes.saml-roles]
20-
title = ""
20+
[notes.extensions]
21+
title = "Extensions Support"
2122
description = """\
22-
Omni can now define SAML user roles depending on the SAML labels it gets from the SAML assertion.
23-
Role is assigned only once on user creation.
23+
It is now possible to change the list of installed extensions for the machines which are allocated into a cluster.
24+
It can be done using cluster templates.
25+
26+
The extensions list can be defined for all machines of a cluster, machine set or for a particular machine.
27+
Extensions update is done the same way as Talos upgrades.
2428
"""

internal/version/data/tag

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v0.30.0
1+
v0.33.0

0 commit comments

Comments
 (0)