Fixed commits fail to publish charms

[addyess]

Notice how our release-branch CI needs to point to a fixed commit of the operator-workflows
Here:
https://github.com/canonical/k8s-operator/blob/release-1.32/.github/workflows/publish-charms.yaml#L44

  publish-to-edge:
    needs: [configure-channel, charmcraft-channel]
    uses: canonical/operator-workflows/.github/workflows/publish_charm.yaml@e848763f1e14d3169781fe95b4b896399a1a8a92
    strategy:
      matrix:
        charm:
        - { path: ./charms/worker/k8s/, tagPrefix: k8s }
        - { path: ./charms/worker/,     tagPrefix: k8s-worker }
        arch:
        - amd64
        - arm64

the publish_charm at that commit

operator-workflows/.github/workflows/publish_charm.yaml

Line 77 in e848763

- uses: canonical/operator-workflows/internal/publish@main

references @main

  publish-charm:
    name: Publish charm to ${{ inputs.channel || needs.select-channel.outputs.destination-channel }}
    runs-on: ubuntu-latest
    needs: [select-channel]
    outputs:
      charm-directory: ${{ steps.publish.outputs.charm-directory }}
    steps:
      - uses: actions/checkout@v4.2.2
      - run: sudo snap install charmcraft --channel ${{ inputs.charmcraft-channel }} --classic
        # required to use skopeo embedded within rockcraft - otherwise a docker error
        # "io: read/write on closed pipe" will happen
      - run: sudo snap install rockcraft --classic
      - uses: canonical/operator-workflows/internal/publish@main

rather than

      - uses: canonical/operator-workflows/internal/publish@e848763f1e14d3169781fe95b4b896399a1a8a92

This basically means you cannot use PINNED versions of the operator-workflow b/c its internally referencing workflows that are unpinned from a commit.

[weiiwang01]

Yes, I think we should consider moving the actions (those in https://github.com/canonical/operator-workflows/tree/main/internal) into a separate repository. The current single repository setup causes the problem you described, where we can't pin the internal actions. It also prevents us from testing changes to the internal actions in pull requests.

[javierdelapuente]

@weiiwang01 do you think it could be interesting to create a Jira story for this issue? I assigned the issue to you, feel free to unassign if needed.

[weiiwang01]

@weiiwang01 do you think it could be interesting to create a Jira story for this issue? I assigned the issue to you, feel free to unassign if needed.

The Jira ticket has already been created by @seb4stien ( thank you :) ) https://warthogs.atlassian.net/browse/ISD-3725. And yes, you can assign the issue to me for now.