Automated update for release v0.12.0

charts/metallb/Chart.yaml

@@ -20,10 +20,10 @@ type: application
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
 # NOTE: this value is updated by the metallb release process
-version: 0.0.0
+version: 0.12.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # NOTE: this value is updated by the metallb release process
-appVersion: v0.0.0
+appVersion: v0.12.0

internal/version/version.go

@@ -8,7 +8,7 @@ import (
 )
 
 var (
-	version   = ""   // Filled out during release cutting
+	version   = "0.12.0"
 	gitCommit string // Provided by ldflags during build
 	gitBranch string // Provided by ldflags during build
 )

manifests/metallb.yaml

@@ -362,7 +362,7 @@ spec:
             secretKeyRef:
               name: memberlist
               key: secretkey
-        image: quay.io/metallb/speaker:main
+        image: quay.io/metallb/speaker:v0.12.0
         name: speaker
         ports:
         - containerPort: 7472
@@ -441,7 +441,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:main
+        image: quay.io/metallb/controller:v0.12.0
         name: controller
         ports:
         - containerPort: 7472

website/content/_header.md

@@ -1,5 +1,5 @@
 ---
 ---
 <img align="left" src="/images/logo/metallb-white.png" width="25%"></img>
-MetalLB (latest version)
+MetalLB v0.12.0
 <p style="clear: both"></p>

website/content/community/_index.md

@@ -59,7 +59,7 @@ information on using pull requests.
 By contributing to this project you agree to the Developer Certificate of
 Origin (DCO). This document was created by the Linux Kernel community and is a
 simple statement that you, as a contributor, have the legal right to make the
-contribution. See the [DCO](https://github.com/metallb/metallb/blob/main/DCO)
+contribution. See the [DCO](https://github.com/metallb/metallb/blob/v0.12.0/DCO)
 file for details.
 
 ## Code organization

website/content/community/maintainers.md

@@ -10,7 +10,7 @@ MetalLB development and maintenance is led by a team of current maintainers.
 MetalLB maintainers are participants in the project with the ability to approve
 changes to the MetalLB code base. The current list of maintainers can be found
 in the [MetalLB CODEOWNERS
-file](https://github.com/metallb/metallb/blob/main/CODEOWNERS).
+file](https://github.com/metallb/metallb/blob/v0.12.0/CODEOWNERS).
 
 ## Maintainer Expectations
 

website/content/configuration/_index.md

@@ -8,7 +8,7 @@ creating and deploying a config map into the same namespace
 (metallb-system) as the deployment.
 
 There is an example config map in
-[`manifests/example-config.yaml`](https://raw.githubusercontent.com/metallb/metallb/main/manifests/example-config.yaml),
+[`manifests/example-config.yaml`](https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/example-config.yaml),
 annotated with explanatory comments.
 
 If you've named the config map `config.yaml`, you can deploy the manifest with `kubectl apply -f config.yaml`.

website/content/installation/_index.md

@@ -59,16 +59,16 @@ kubectl apply -f - -n kube-system
 To install MetalLB, apply the manifest:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/main/manifests/namespace.yaml
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/main/manifests/metallb.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/namespace.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/metallb.yaml
 ```
 
 {{% notice note %}}
 If you want to deploy MetalLB using the [experimental FRR mode](https://metallb.universe.tf/configuration/#enabling-bfd-support-for-bgp-sessions), apply the manifests:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/main/manifests/namespace.yaml
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/main/manifests/metallb-frr.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/namespace.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/metallb-frr.yaml
 ```
 
 Please do note that these manifests deploy MetalLB from the main development branch. We highly encourage cloud operators to deploy a stable released version of MetalLB on production environments!
@@ -121,7 +121,7 @@ the config map, as MetalLB is waiting for a config map named `config`
 namespace: metallb-system
 
 resources:
-  - github.com/metallb/metallb//manifests?ref=v0.11.0
+  - github.com/metallb/metallb//manifests?ref=v0.12.0
 
 configMapGenerator:
 - name: config

website/content/release-notes/_index.md

@@ -694,7 +694,7 @@ New features:
   topologies.
 - MetalLB now has
   a
-  [Helm chart](https://github.com/metallb/metallb/tree/main/helm/metallb). If
+  [Helm chart](https://github.com/metallb/metallb/tree/v0.12.0/helm/metallb). If
   you use [Helm](https://helm.sh) on your cluster, this should make it
   easier to track and manage your MetalLB installation. The chart will
   be submitted for inclusion in the main Helm stable repository
@@ -752,7 +752,7 @@ Action required if upgrading from 0.2.x:
   ds/bgp-speaker`. This will take down your load balancers until you
   deploy the new DaemonSet.
 - The
-  [configuration file format](https://raw.githubusercontent.com/metallb/metallb/main/manifests/example-config.yaml) has
+  [configuration file format](https://raw.githubusercontent.com/metallb/metallb/v0.12.0/manifests/example-config.yaml) has
   changed in a few backwards-incompatible ways. You need to update
   your ConfigMap by hand:
   - Each `address-pool` must now have a `protocol` field, to select