update actions relative pathing

Author: clavery

action.yml

@@ -77,7 +77,7 @@ runs:
   steps:
     - name: Setup B2C CLI
       id: setup
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -97,7 +97,7 @@ runs:
     - name: Run command
       id: command
       if: inputs.command != ''
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: ${{ inputs.command }}
         json: ${{ inputs.json }}

actions/README.md

@@ -156,3 +156,5 @@ When `json: true` (default), the `result` output contains the parsed JSON from t
   with:
     version: '0.4.1'  # Pin CLI version
 ```
+
+> **Note:** High-level actions (`code-deploy`, `data-import`, `job-run`, `mrt-deploy`, `webdav-upload`) and the root action internally reference `actions/setup@v1` and `actions/run@v1`. This means even if you pin the outer action to a specific SHA or tag, the setup and run steps resolve to the latest `v1` release. For full SHA-level reproducibility, use `actions/setup` + `actions/run` directly — each can be pinned independently to an exact SHA. For most users, `@v1` on the high-level actions is the recommended approach.

actions/code-deploy/action.yml

@@ -64,7 +64,7 @@ runs:
   using: 'composite'
   steps:
     - name: Ensure CLI is installed
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -113,7 +113,7 @@ runs:
 
     - name: Deploy cartridges
       id: deploy
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: ${{ steps.build-cmd.outputs.cmd }}
         json: 'true'

actions/data-import/action.yml

@@ -57,7 +57,7 @@ runs:
   using: 'composite'
   steps:
     - name: Ensure CLI is installed
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -89,7 +89,7 @@ runs:
 
     - name: Import data
       id: import
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: ${{ steps.build-cmd.outputs.cmd }}
         json: 'true'

actions/job-run/action.yml

@@ -55,7 +55,7 @@ runs:
   using: 'composite'
   steps:
     - name: Ensure CLI is installed
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -91,7 +91,7 @@ runs:
 
     - name: Run job
       id: job
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: ${{ steps.build-cmd.outputs.cmd }}
         json: 'true'

actions/mrt-deploy/action.yml

@@ -47,7 +47,7 @@ runs:
   using: 'composite'
   steps:
     - name: Ensure CLI is installed
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -85,7 +85,7 @@ runs:
 
     - name: Deploy MRT bundle
       id: deploy
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: ${{ steps.build-cmd.outputs.cmd }}
         json: 'true'

actions/webdav-upload/action.yml

@@ -53,7 +53,7 @@ runs:
   using: 'composite'
   steps:
     - name: Ensure CLI is installed
-      uses: ./actions/setup
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/setup@v1
       with:
         version: ${{ inputs.version }}
         node-version: ${{ inputs.node-version }}
@@ -65,7 +65,7 @@ runs:
 
     - name: Upload via WebDAV
       id: upload
-      uses: ./actions/run
+      uses: SalesforceCommerceCloud/b2c-developer-tooling/actions/run@v1
       with:
         command: "webdav put ${{ inputs.local-path }} ${{ inputs.remote-path }} --root ${{ inputs.root }}"
         json: 'true'

docs/guide/ci-cd.md

@@ -390,6 +390,8 @@ Use the `version` input to pin the CLI version:
 
 Use `@v1` for the latest stable action version (recommended). The floating `v1` tag is updated on each backward-compatible release.
 
+> **Note:** High-level actions (`code-deploy`, `data-import`, `job-run`, `mrt-deploy`, `webdav-upload`) and the root action internally reference `actions/setup@v1` and `actions/run@v1`. This means even if you pin the outer action to a specific SHA or tag, the setup and run steps resolve to the latest `v1` release. For full SHA-level reproducibility, use `actions/setup` + `actions/run` directly — each can be pinned independently to an exact SHA. For most users, `@v1` on the high-level actions is the recommended approach.
+
 ## Plugins
 
 The CLI supports [plugins](/guide/extending) for custom configuration sources, HTTP middleware, and more. Install plugins in CI with the `plugins` input on the `setup` action: