Fail to load /home/runner/work/_actions/actions/setup-java/v1/action.yml

Hi. Somewhy this action stopped working for me.

I get this output:

2019-11-22T20:29:03.8282479Z ##[section]Starting: Request a runner to run this job
2019-11-22T20:29:04.4018077Z Requesting a hosted runner in current repository's account/organization with labels: 'ubuntu-latest', require runner match: True
2019-11-22T20:29:04.4718879Z Labels matched hosted runners has been found, waiting for one of them get assigned for this job.
2019-11-22T20:29:04.5111217Z ##[section]Finishing: Request a runner to run this job
2019-11-22T20:29:12.7823163Z Current runner version: '2.160.2'
2019-11-22T20:29:12.7824338Z Prepare workflow directory
2019-11-22T20:29:12.8056056Z Prepare all required actions
2019-11-22T20:29:12.8084669Z Download action repository 'actions/checkout@v1'
2019-11-22T20:29:13.7985549Z Download action repository 'actions/setup-java@v1'
2019-11-22T20:29:14.6419126Z ##[error]/home/runner/work/_actions/actions/setup-java/v1/action.yml:
2019-11-22T20:29:14.6533927Z ##[error]/home/runner/work/_actions/actions/setup-java/v1/action.yml: (Line: 16, Col: 3, Idx: 552) - (Line: 16, Col: 3, Idx: 552): While parsing a block mapping, did not find expected key.
2019-11-22T20:29:14.6536021Z ##[error]Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected.
2019-11-22T20:29:14.6557498Z ##[error]Fail to load /home/runner/work/_actions/actions/setup-java/v1/action.yml

My input:

name: Java CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v1
      
    - name: Set up JDK 1.8
      uses: actions/setup-java@v1
      with:
        java-version: 1.8

[konradpabjan]

yes, v1.2.0 and v1 tying are done via tags.

I’m contemplating deleting the v1.0 tag or at least making it align with v1 until we have a v2 tag (I’ll most likely align it so that no existing workflows break) . In all our other actions such as setup-python and upload-artifact there is only tags for v1 or v1.x.x.

[konradpabjan]

v1 should work now. #30 fixed the issue we were having. Did some testing and it looks to be working

v1.2.0 and v1 should now be tied to the commit that fixed the issue