Camel CLI installers and documentation - #1699
Merged
Merged
Conversation
Per-version SHA-256 manifests (format=1, version, tar_sha256, zip_sha256) for every camel-launcher release with -bin archives on Maven Central, plus latest.properties pointing at 4.21.0. The 4.21.0 manifest matches the test fixture in apache/camel's WebsiteInstallerFixture; the rest are computed directly from the published -bin.tar.gz/-bin.zip archives. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
install.sh / install.ps1 fetched byte-identical from apache/camel main (dsl/camel-jbang/camel-launcher/src/install). Do not edit here; regenerate with ./update-camel-cli-manifest.sh. Manifests for 4.13.0-4.21.0 were published in a prior commit.
- Link to the installers directory in apache/camel instead of the PR - Match the voice of recent posts (direct, concrete, no filler) - Lead with how much friction the installer removes vs. jbang setup - Add a real camel init/camel run example with verified output
ammachado
changed the title
ammachado
changed the title
ammachado
changed the title
davsclaus
approved these changes
Jul 20, 2026
davsclaus
left a comment
davsclaus
left a comment
Contributor
There was a problem hiding this comment.
Reviewed against project conventions — no issues found.
Security model is solid:
- Archive from Maven Central verified against SHA-256 checksum from camel.apache.org (two independent hosts)
- Archive contents validated before extraction (no absolute paths, no traversal, no symlinks, single top-level directory)
- Staged launcher verified (Java 17+ check) before activation — failure leaves prior install untouched
- Manifest parsing uses line-by-line reads without eval/source/dot-invoke
- Per-user install only, never requires sudo/elevation
Content is clean:
- Blog post covers one-line install, zero-to-running-route, security verification, and links to the guide
- Installation guide covers requirements, quick install, inspect-before-run workflow, and security explanation
- Download index addition is minimal and well-placed
This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.
ammachado
added a commit
to ammachado/camel-website
that referenced
this pull request
Jul 21, 2026
* feat: publish Camel CLI Launcher manifests for 4.13.0 through 4.21.0 Per-version SHA-256 manifests (format=1, version, tar_sha256, zip_sha256) for every camel-launcher release with -bin archives on Maven Central, plus latest.properties pointing at 4.21.0. The 4.21.0 manifest matches the test fixture in apache/camel's WebsiteInstallerFixture; the rest are computed directly from the published -bin.tar.gz/-bin.zip archives. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * feat: add Camel CLI Launcher manifest publishing helper * feat: publish Camel CLI Launcher installers install.sh / install.ps1 fetched byte-identical from apache/camel main (dsl/camel-jbang/camel-launcher/src/install). Do not edit here; regenerate with ./update-camel-cli-manifest.sh. Manifests for 4.13.0-4.21.0 were published in a prior commit. * docs: add Camel CLI Launcher installation guide * blog: announce the Camel CLI Launcher installers * blog: revise Camel CLI Launcher post for voice and a route example - Link to the installers directory in apache/camel instead of the PR - Match the voice of recent posts (direct, concrete, no filler) - Lead with how much friction the installer removes vs. jbang setup - Add a real camel init/camel run example with verified output * blog: add featured image to Camel CLI Launcher installers post --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
install.sh/install.ps1one-line installers for the Camel CLI Launcher, plus per-version release manifests (4.13.0 through 4.21.0) and a helper script to publish new manifests (Add Install scripts for Camel Launcher #1487).Test plan (after publishing)
install.shandinstall.ps1are reachable and served correctly once merged