Skip to content

Releases: meshcloud/actions-register-source

v2.0.2

15 Dec 14:08
62ed10e

Choose a tag to compare

What's Changed

Full Changelog: v2...v2.0.2

v2.0.1

15 Dec 13:39
ccc68ba

Choose a tag to compare

What's Changed

Full Changelog: v2.0.0...v2.0.1

v2.0.0

10 Dec 16:03
71d0406

Choose a tag to compare

Breaking Changes

  • Node.js Runtime Update: Migrated from Node.js 20 to Node.js 24

    • Ensure your GitHub Actions runners support Node.js 24
    • Update your workflow files to reference @v2 instead of previous versions
  • Authentication Separation: Authentication is now handled by a separate action (actions-meshstack-auth)

    • Required: You must now call meshcloud/actions-meshstack-auth@v2 before using this action
    • Removed client_id, key_secret, and base_url inputs from this action
    • This action now reads authentication tokens from a well-known file location
  • Input Changes:

    • Added support for the new buildingBlockRunUrl dispatch input. This input method allows you to pass more than 64kB of inputs to a building block run. The action automatically extracts either buildingBlockRunUrl or buildingBlockRun from the dispatch event payload depending on what is available

Migration Guide

To migrate from v0.x to v2:

  1. Add authentication step before using this action:

    - name: Setup meshStack auth
      id: setup-meshstack-auth
      uses: meshcloud/actions-meshstack-auth@v2
      with:
        base_url: ${{ vars.MESHSTACK_BASE_URL }}
        client_id: ${{ vars.BUILDINGBLOCK_API_CLIENT_ID }}
        key_secret: ${{ secrets.BUILDINGBLOCK_API_KEY_SECRET }}
  2. Update action reference and remove authentication inputs:

    # OLD (v1)
    - uses: meshcloud/actions-register-source@v1
      with:
        client_id: ${{ vars.BUILDINGBLOCK_API_CLIENT_ID }}
        key_secret: ${{ secrets.BUILDINGBLOCK_API_KEY_SECRET }}
        steps: |
          [...]
    
    # NEW (v2)
    - uses: meshcloud/actions-register-source@v2
      with:
        steps: |
          [...]
  3. Recommended: Ensure workflow_dispatch event uses new buildingBlockRunUrl parameter

  • update your building block definition in meshStack to select this method

  • ensure your API Key has the permission List building block runs using building block definitions or runners owned by this workspace

  • replace workflow_dispatch.inputs.buildingBlockRun with workflow_dispatch.inputs.buildingBlockRunUrl in your workflow

    on:
      workflow_dispatch:
        inputs:
          buildingBlockRunUrl:
            description: "URL to fetch the Building Block Run Object from"
            required: true

Full Changelog: v0.1.0...v2.0.0

v0.1.0

08 Nov 12:20

Choose a tag to compare

Full Changelog: v0.0.16...v0.1.0

v0.0.16

06 Nov 17:30

Choose a tag to compare

Full Changelog: v0.0.15...v0.0.16

v0.0.15

06 Nov 10:31

Choose a tag to compare

Full Changelog: v0.0.14...v0.0.15

v0.0.14

06 Nov 09:55

Choose a tag to compare

Full Changelog: v0.0.13...v0.0.14

v0.0.13

06 Nov 09:35

Choose a tag to compare

Full Changelog: v0.0.12...v0.0.13

v0.0.12

06 Nov 09:33

Choose a tag to compare

Full Changelog: v.0.0.11...v0.0.12

v0.0.11

05 Nov 15:12

Choose a tag to compare

Full Changelog: 0.0.1...v0.0.11