feat: distribute the CLI as a dpm component

.changeset/dpm-component-channel.md

@@ -0,0 +1,9 @@
+---
+"@bootnodedev/canton-barebones": minor
+---
+
+Add a dpm distribution channel: the CLI is now also published as a dpm component
+(`oci://ghcr.io/bootnodedev/canton-barebones`) with self-contained binaries for
+linux/darwin/windows — no Node required. Install it by declaring the component in
+`daml.yaml` and running `dpm install package`, then use `dpm canton-barebones <cmd>`
+(alias `dpm cbn`). The npm channel is unchanged.

.github/actions/setup-dpm/action.yml

@@ -0,0 +1,26 @@
+# Installs the dpm CLI, pinned by version and checksum.
+#
+# Single source of truth for which dpm both workflows run: ci.yml (validates
+# the component with a publish --dry-run) and release.yml (publishes it to
+# ghcr). Bumping dpm means editing the two values below in a PR — where the CI
+# dry-run exercises the new version before it can ever touch a release.
+# The pin matters because dpm assembles and pushes artifacts in our name: a new
+# dpm release must never silently change what the pipelines execute.
+name: Setup dpm
+description: Install the dpm CLI, pinned by version and sha256 checksum
+
+runs:
+  using: composite
+  steps:
+    - name: Install dpm
+      shell: bash
+      env:
+        DPM_VERSION: 1.0.21
+        DPM_SHA256: 71061e3ecee029bc88ccfc1b51367e3257162f3bd91c7edcc688af503fef5e59
+      run: |
+        curl -fsSL -o dpm.tar.gz "https://github.com/digital-asset/dpm/releases/download/${DPM_VERSION}/dpm-${DPM_VERSION}-linux-amd64.tar.gz"
+        echo "${DPM_SHA256}  dpm.tar.gz" | sha256sum -c -
+        tar -xzf dpm.tar.gz dpm
+        rm dpm.tar.gz
+        sudo mv dpm /usr/local/bin/dpm
+        dpm --version

.github/workflows/ci.yml

@@ -0,0 +1,73 @@
+# PR validation: unit tests plus a full dpm-component build check.
+#
+# The component job cross-compiles the CLI for every supported platform and
+# runs `dpm publish component --dry-run`, which is dpm's own validation of the
+# manifest and layout (including the LICENSE-at-component-root requirement).
+# Nothing is published here — the real publish happens in release.yml when a
+# Version Packages PR lands.
+name: CI
+
+on:
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - run: npm ci
+
+      - run: npm test
+
+  component:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      # Bun is the cross-compiler for the standalone binaries (see
+      # scripts/build-component.js). Pinned for reproducible binaries.
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.3.1
+
+      # The compiled binary bundles the runtime dependencies (zod), so they
+      # must be installed before Bun can resolve them.
+      - run: npm ci
+
+      - run: npm run build:component
+
+      # Pinned dpm shared with release.yml — see the action for the pin rationale.
+      - uses: ./.github/actions/setup-dpm
+
+      # The version tag is a placeholder: --dry-run never contacts a registry,
+      # but dpm still requires a syntactically valid oci:// URI with strict
+      # semver. The -p flags must cover exactly the platforms the build emits
+      # (scripts/build-component.js prints this same command on every run).
+      - name: Validate component (dpm publish --dry-run)
+        run: |
+          dpm publish component 'oci://ghcr.io/bootnodedev/canton-barebones:0.0.0' \
+            -p linux/amd64=dist/dpm-component/linux-amd64 \
+            -p linux/arm64=dist/dpm-component/linux-arm64 \
+            -p darwin/amd64=dist/dpm-component/darwin-amd64 \
+            -p darwin/arm64=dist/dpm-component/darwin-arm64 \
+            -p windows/amd64=dist/dpm-component/windows-amd64 \
+            --dry-run
+
+      # The linux-amd64 binary can run right here: make sure a compiled binary
+      # actually executes and scaffolds from its embedded templates.
+      - name: Smoke-test the linux binary
+        run: |
+          mkdir smoke && cd smoke
+          ../dist/dpm-component/linux-amd64/canton-barebones init
+          test -f canton-barebones.config.json
+          test -f splice-localnet-overrides.yaml

.github/workflows/release.yml

@@ -1,9 +1,12 @@
-# Publishes @bootnodedev/canton-barebones to npm via Changesets.
+# Publishes @bootnodedev/canton-barebones to npm via Changesets, and the dpm
+# component (standalone binaries) to ghcr.io.
 #
 # Flow: every push to main runs this. The changesets action either
 #   (a) opens/updates a "Version Packages" PR when unreleased changesets exist, or
 #   (b) publishes to npm when that PR was merged (i.e. package.json version bumped).
 # Nothing is published on a normal merge — only when the Version Packages PR lands.
+# The dpm component is published right after a successful npm publish, with the
+# same version, so both channels always ship the same source.
 name: Release
 
 on:
@@ -20,6 +23,7 @@ jobs:
       contents: write # create tags / GitHub releases and push the Version Packages PR
       pull-requests: write # open and update the Version Packages PR
       id-token: write # npm trusted publishing (OIDC) and provenance
+      packages: write # push the dpm component to ghcr.io
     steps:
       - uses: actions/checkout@v4
         with:
@@ -41,8 +45,44 @@ jobs:
       - run: npm test
 
       - name: Create Version PR or publish
+        id: changesets
         uses: changesets/action@v1
         with:
           publish: npm run release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      # Everything below runs only when the step above actually published to npm
+      # (the Version Packages PR was merged); ordinary merges skip it entirely.
+
+      - uses: oven-sh/setup-bun@v2
+        if: steps.changesets.outputs.published == 'true'
+        with:
+          bun-version: 1.3.1 # keep in sync with ci.yml
+
+      # Pinned dpm shared with ci.yml — see the action for the pin rationale.
+      - uses: ./.github/actions/setup-dpm
+        if: steps.changesets.outputs.published == 'true'
+
+      - name: Publish dpm component to ghcr.io
+        if: steps.changesets.outputs.published == 'true'
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          npm run build:component
+
+          # dpm reads registry credentials from docker's config.json, so a
+          # regular docker login is all the auth it needs.
+          echo "$GITHUB_TOKEN" | docker login ghcr.io -u "$GITHUB_ACTOR" --password-stdin
+
+          # The npm publish already bumped package.json, so its version is the
+          # single source of truth for both channels. dpm requires strict semver
+          # tags; --extra-tags latest lets users pin `:latest` in daml.yaml.
+          VERSION=$(node -p "require('./package.json').version")
+          dpm publish component "oci://ghcr.io/bootnodedev/canton-barebones:${VERSION}" \
+            -p linux/amd64=dist/dpm-component/linux-amd64 \
+            -p linux/arm64=dist/dpm-component/linux-arm64 \
+            -p darwin/amd64=dist/dpm-component/darwin-amd64 \
+            -p darwin/arm64=dist/dpm-component/darwin-arm64 \
+            -p windows/amd64=dist/dpm-component/windows-amd64 \
+            --extra-tags latest

.gitignore

@@ -8,3 +8,6 @@ node_modules/
 /canton-barebones.config.json
 /splice-localnet-overrides.yaml
 
+
+# Compiled standalone binaries (npm run build:binary)
+dist/

LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.