Unable to resolve action actions/labeler@v4.2.0, unable to find version v4.2.0

[ekosman]

I want to use the outputs of a labeler step in order to selectively run tests based on the added labels. For this, I understand I need v4.2.0. However, I get the following error:

Unable to resolve action `actions/labeler@v4.2.0`, unable to find version `v4.2.0`

Additionally, I think there is a mistake in README. It says install v3:

    steps:
    - id: label-the-PR
      uses: actions/labeler@v3

[dusan-trickovic]

Hello @ekosman ! Thank you for creating this issue. We will investigate it and see what can be done :)

[MaksimZhukov]

Hello @ekosman!
I could not reproduce your issue, I was able to use the v4.2.0 tag. Could you please provide us with a link to your workflow run?

Have you tried using the v4 tag? It points to the same commit as v4.2.0.

Thank you for noticing a typo in the documentation. We are fixing it in this pull request.

[ekosman]

Hello @ekosman! I could not reproduce your issue, I was able to use the v4.2.0 tag. Could you please provide us with a link to your workflow run?

Have you tried using the v4 tag? It points to the same commit as v4.2.0.

Thank you for noticing a typo in the documentation. We are fixing it in this pull request.

Thanks! Unfortunately, I can't share the workflow run here but for instance I have this snipper in my yml file:

    steps:
      - name: Label and comment PR size
        if: github.event_name == 'pull_request'
        uses: boschresearch/pr-size-labeler@v3.0.0
        # Uncomment these if you want to use your own custom configuration
        #with:
        #  bucketConfigFile: "<PATH_TO_YOUR_BUCKET_CONFIG>"

      - name: Label type
        id: label-the-PR
        if: github.event_name == 'pull_request'
        uses: actions/labeler@v4

      - name: print labels
        run: |
          echo ${{ steps.label-the-PR.outputs.all-labels }}

In the PR, I see the added labels:

However, when checking the output of print labels step, I see nothing:

[MaksimZhukov]

I could not reproduce your issue. I created a public repository for the test, please take a look:

1. Workflow file
2. Workflow run
3. Related PR

Could you please prepare a public simple repository where the issue occurs for further investigation?

[ekosman]

Thanks for checking. I've identified the source for the problem and now it works.

[raja-anbazhagan]

By the look of the GitHub actions bot logo, this run is from a GitHub Enterprise Server for a private organization set up. They usually have all official actions synced to their instance only at new updates.

If you face similar issues in a similar situation, you might want to ask your administrators to manually sync those specific repositories if you need them.