move main to next minor release (#4960)

Author: jharvey10

CHANGELOG.md

@@ -34,7 +34,7 @@ Main (unreleased)
 - (_Public Preview_) Additions to `database_observability.mysql` component:
   - replace the internal `server_id` label attribution in favor of a hash composed from `@@server_uuid` and `@@hostname`
 
-v1.12.0-rc.3
+v1.12.0
 -----------------
 
 ### Breaking changes

VERSION

@@ -20,4 +20,4 @@
 #
 # Lines starting with "#" and blank lines are ignored.
 
-v1.12.0
+v1.13.0

docs/developer/release/02-update-version-in-code.md

@@ -80,12 +80,12 @@ For an Additional Release Candidate or SRV, update the header `PREVIOUS_RELEASE_
 
 ### 2.2. Update the VERSION file
 
-The [VERSION file][VERSION-file] on the "main" branch should point to the next major version.
+The [VERSION file][VERSION-file] on the "main" branch should point to the next minor version.
 For example:
 * If you are going to release `v1.2.0-rc.0`, then the VERSION file should contain `v1.3.0`.
 * If you are going to release `v1.5.1`, then the VERSION file should contain `v1.6.0`.
 
-The reasoning behind this is that any builds of the main branch should contain the next major version they are meant to go to.
+The reasoning behind this is that any builds of the main branch should contain the next minor version they are meant to go to.
 If the latest release branch that was cut is `release/1.3`, then `main` is preparing for `1.4.0`.
 Any builds of the main branch will therefore be labeled `devel-1.4.0`.
 

docs/sources/_index.md

@@ -4,7 +4,7 @@ title: Grafana Alloy
 description: Grafana Alloy is a vendor-neutral distribution of the OTel Collector
 weight: 350
 cascade:
-  ALLOY_RELEASE: v1.12.0
+  ALLOY_RELEASE: v1.13.0
   OTEL_VERSION: v0.139.0
   PROM_WIN_EXP_VERSION: v0.31.3
   SNMP_VERSION: v0.29.0