This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new e318726baa02 chore: document camel-publish.sh in the release guide
(#25473)
e318726baa02 is described below
commit e318726baa026771a17949d98404cfc0545b7c75
Author: Adriano Machado <[email protected]>
AuthorDate: Wed Aug 12 12:02:54 2026 -0400
chore: document camel-publish.sh in the release guide (#25473)
camel-publish.sh (dsl/camel-jbang/camel-launcher/src/jreleaser/bin) drives
the JReleaser publish for camel-cli to Homebrew, the Camel website, WinGet,
Scoop, SDKMAN and Chocolatey, but none of these destinations were documented
in the release guide.
Co-authored-by: Claude Sonnet 5 <[email protected]>
---
.../modules/ROOT/pages/release-guide.adoc | 30 ++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/pages/release-guide.adoc
b/docs/user-manual/modules/ROOT/pages/release-guide.adoc
index 317e1ff33de8..fcf7a489b4da 100644
--- a/docs/user-manual/modules/ROOT/pages/release-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/release-guide.adoc
@@ -447,6 +447,36 @@ approved local ZIP.
git branch -D release/VERSION
git push origin --delete release/VERSION
+[[ReleaseGuide-PublishingCamelCli]]
+== Publishing camel-cli packages
+
+Once the `camel-launcher` binary artifacts
(`camel-launcher-<version>-bin.tar.gz` / `.zip`) have
+been built and staged, `camel-publish.sh` drives the JReleaser-based publish
to the camel-cli
+package destinations. It is a single resumable orchestrator, not something
invoked destination by
+destination.
+
+ cd ${CAMEL_ROOT_DIR}/dsl/camel-jbang/camel-launcher/src/jreleaser/bin
+ ./camel-publish.sh <Camel version> --channel stable|lts [--lts-line X.Y]
+
+* `--channel lts` requires `--lts-line X.Y` (e.g. `--lts-line 4.18`) and
targets a versioned
+Homebrew formula (`[email protected]`); `--channel stable` targets the
unversioned formula
+(`apache-camel`).
+* Required environment: `GITHUB_TOKEN`, `SDKMAN_CONSUMER_KEY`,
`SDKMAN_CONSUMER_SECRET`,
+`CHOCO_API_KEY`.
+* The `homebrew-core` and `winget-pkgs` destinations push to your own fork,
not upstream. Fork
+both repositories first (`gh repo fork homebrew/homebrew-core --clone=false`
and
+`gh repo fork microsoft/winget-pkgs --clone=false`) and make sure the
`FORK_REMOTE`/
+`CAMEL_PUB_FORK_REMOTE` git remote used by the script is configured before
running it.
+
+The script publishes to destinations in this order: JReleaser package →
Homebrew tap → Camel
+website → WinGet → Scoop → SDKMAN → Chocolatey. `--channel lts` skips Scoop
and SDKMAN (no
+versioned Scoop manifest, and SDKMAN only tracks the latest stable release).
+
+Progress is recorded in `target/jreleaser/publish-state.json`; re-running the
same command after a
+partial failure resumes from the first incomplete destination instead of
repeating completed ones.
+The script never merges the PRs it opens against `homebrew-core` or
`winget-pkgs` — merge timing
+for those is up to each project's own maintainers.
+
[[Publish-xsd-schemas]]
== Publish xsd schemas
