ammachado opened a new pull request, #25473:
URL: https://github.com/apache/camel/pull/25473

   # Description
   
   `camel-publish.sh` 
(`dsl/camel-jbang/camel-launcher/src/jreleaser/bin/camel-publish.sh`) is the
   resumable orchestrator that publishes camel-cli release artifacts to 
JReleaser, Homebrew,
   the Camel website, WinGet, Scoop, SDKMAN and Chocolatey, but none of these 
destinations were
   documented in `release-guide.adoc`. This adds a "Publishing camel-cli 
packages" section covering
   usage, required environment variables, the fork prerequisites for the 
Homebrew/WinGet
   destinations, the publish order, and the resumable state-file behavior.
   
   Docs-only change, no code touched.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   
   - [ ] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   Trivial documentation fix, no JIRA issue filed per the template's own note 
on trivial changes.
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [ ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   Docs-only `.adoc` change; not applicable (no generated code to regenerate).
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   _Claude Code on behalf of ammachado_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to