Cannot find serverless/github-action@v4

[mihirgupta0900]

I was using the v4 of the action (as mentioned here: #91 (comment)) and was working find until yesterday.

Currently facing this error:

Error: Unable to resolve action `serverless/github-action@v4`, unable to find version `v4`

I do not see a v4 release and looks like this could be caused when this PR was merged: #97

This is currently blocking us and I think a new release needs to be published to fix this issue

[Andriy-Kulak]

I am getting the same issue :-(. I cannot deploy serverless using github actions.

@eahefnawy or @skierkowski - was anything changed in the last couple of days since I brought a related issue serverless/serverless#12967 up?

[skierkowski]

@czubocha can you have a look?

[mihirgupta0900]

Here's what I'm currently doing to deploy:

      - name: Install Serverless
        run: npm install -g serverless

      - name: NPM Install
        run: npm install

      - name: Serverless Deploy
        run: serverless deploy --debug --stage ${{ env.DGN }} --region ${{ env.AWS_REGION }} --force
        env:
          SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}

[Andriy-Kulak]

thanks for the reference @mihirgupta0900. will try that on monday.

@czubocha @skierkowski, in case extra context is helpful, below is my simplified yaml github action config that is causing the "unable to resolve serverless/github-action@v4" error

name: ...
jobs:
  deploy:
    name: Deploy functions
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [20.x]
    steps:
      - uses: actions/checkout@v4

      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}
          cache: "yarn"

      - run: yarn install --frozen-lock-file

      - name: serverless deploy
        if: github.ref == 'refs/heads/main'
        uses: serverless/github-action@v4
        with:
          args: deploy --stage production

[cameronmurphy]

Same issue here, has worked for ages despite there being no 4.0 tag for this repo, but randomly just stopped working.

For anyone whose deployment pipeline this is breaking, this fork is a drop in replacement.

[Mmarzex]

Sorry guys, we merged the v4 branch and didn't realize the branch got deleted. This should be fixed now.