You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2026/09/07 13:06:40 UTC

(camel-k) branch main updated: chore: release procedure polish

This is an automated email from the ASF dual-hosted git repository.

squakez pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/main by this push:
     new 6b765eaa1 chore: release procedure polish
6b765eaa1 is described below

commit 6b765eaa12bfdb76aebf00a83c9e4bb5942ce4ca
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Mon Sep 7 15:06:33 2026 +0200

    chore: release procedure polish
---
 release.adoc | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/release.adoc b/release.adoc
index 29c819eae..7d2fd63ba 100644
--- a/release.adoc
+++ b/release.adoc
@@ -197,24 +197,18 @@ An Helm chart was generated during the staging procedure. Use the commit ID to c
 
 After this is done, wait for them to be available on https://hub.helm.sh/ (generally within some hour after the cherry-pick).
 
-=== Homebrew
-
-The https://brew.sh/[HomeBrew] formula for _kamel_ must be synced to download and build the latest version of https://github.com/apache/camel-k[Camel K], so it can be easily installed on _macOs_ and _Linux_ platforms.
-
-NOTE: it seems it exist an automatic process in charge to update Brew formula as soon as there is a release. Check it out if after the release, https://github.com/Homebrew/homebrew-core/pulls?q=is%3Apr+kamel+is%3Aclosed[a pull request with the new version for kamel] is automatically done.
-
 == Finalize the release
 
 The release is complete, we only need to make it official:
 
 === Official Apache documentation page
 
-The version of Camel K and the main related dependencies are scraped automatically in a Github Action. You only need to provide the LTS parameter in the related `release` branch, when the release is marked as LTS (such as in https://github.com/apache/camel-k/blob/f15124949e43bb859d07f555b9e510956d6ed823/docs/antora.yml#L30). You also need to make sure that the `antora.yml` file has correctly set the version (which may be still set as `main`) and the `prerelease` tag (which should be remo [...]
+The version of Camel K and the main related dependencies are scraped automatically in a Github Action.
 
 After the vote has passed you should update camel-website project:
 
 1. update the https://github.com/apache/camel-website/blob/main/antora-playbook-snippets/antora-playbook.yml[camel-website `antora-playbook.yml` `content.sources` section] for camel-k to use the newly released versions, replacing the previous released version or any unsupported version.
-2. update the https://github.com/apache/camel-k/blob/release-2.5.x/docs/antora.yml[camel k release branch] antora configuration.
+2. update the https://github.com/apache/camel-k/blob/release-2.5.x/docs/antora.yml[camel k release branch] antora configuration (proper version name, last release and remove pre-release labels).
 3. create an entry in the release section of Camel website project: https://github.com/apache/camel-website/tree/main/content/releases/k - you can use any previous document as a reference.
 4. provide a blog post announcing the release