search

googleapis / release-please-action

automated releases based on conventional commits
Apache License 2.0
1.61k stars 207 forks source link

Error: release-please failed: Not Found (On repo working yesterday) #928

Closed aaronware closed 7 months ago

aaronware commented 7 months ago

TL;DR

Started happening this morning. Also tried generating a new token in case it had something to do with with that. However it threw the same error

Expected behavior

Create a release

Observed behavior

Error

Action YAML

on:
  push:
    branches:
      - main

permissions:
  contents: write
  pull-requests: write

name: release-please

jobs:
  release-please:
    if: github.event_name != 'pull_request' && github.event.pull_request.merged != true
    runs-on: ubuntu-latest
    outputs:
      release_created: ${{ steps.release.outputs.release_created }}
    steps:
      - uses: google-github-actions/release-please-action@v4
        id: release
        with:
          token: ${{ secrets.GH_BOT_TOKEN }}

Log output

Run google-github-actions/release-please-action@v4
Running release-please version: 16.5.0
❯ Fetching release-please-config.json from branch main
❯ Fetching .release-please-manifest.json from branch main
✔ Building releases
✔ Building strategies by path
❯ .: php
❯ Found pull request #44: 'chore(main): release 1.0.9'
✔ Building release for path: .
❯ type: php
❯ targetBranch: main
✔ Creating 1 releases for pull #44
Error: release-please failed: Not Found

Additional information

No response

aaronware commented 7 months ago

If anyone comes across this issue and it's not related to an expired token. For some reason the merged branch never received the actual release and the pending tag was still being read for a branch that was already merged.

For this error at the time our version was 1.0.9 our project. I had to go into the existing 1.0.9 and merged (pull request) and remove the pending tag. This allowed the release-please action to run again.