googleapis / googleapis/release-please-action

release-please failed: Invalid request - "sha" wasn't supplied

Open
#959 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
2.5k
Forks
327
PR merge metrics
No merged PRs in 30d

Description

### TL;DR

[error]release-please failed: Invalid request.
"sha" wasn't supplied.
(Same behavior on v4)

### Expected behavior

No failure

### Observed behavior

Failure

### Action YAML

```yaml
on:
push:
branches:
- main

permissions:
contents: write
pull-requests: write

name: Release Please

jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@v3
with:
token: ${{ secrets.BUILDBOT_PAT }}
release-type: simple
# config-file: release-please-config.json
# manifest-file: .release-please-manifest.json
```

### Log output

```text
2024-03-15T10:38:12.1460651Z ❯ commit could not be parsed: 73455ce1000991085c58de4cd3f6f7b7df7f6a33 Use new Core drag feature instead of legacy version (#1050)
2024-03-15T10:38:12.1728025Z ❯ commit could not be parsed: 36060935d72c3e6e5fb5b42044f03d2281f7e9a7 jid-262-Assess-TypeScript-settings (#1007)
2024-03-15T10:38:12.1938927Z ❯ commit could not be parsed: e8ddf65f669ca6272229bc2a9db1dc149ee45b28 Merge pull request #987 from org/jid-949-update-dora-metrics-endpoint
2024-03-15T10:38:12.1941999Z ❯ commit could not be parsed: 34a20d05e3b182017e5147f98ac9c412e8ba2982 Dummy commit to trigger again dora_start action
2024-03-15T10:38:12.2472793Z ❯ commits: 1009
2024-03-15T10:38:12.2474038Z ⚠ No latest release pull request found.
2024-03-15T10:38:12.2477029Z ✔ Considering: 1009 commits
2024-03-15T10:38:12.2484848Z ❯ component:
2024-03-15T10:38:12.2486505Z ❯ pull request title pattern: undefined
2024-03-15T10:38:12.6653265Z ✔ Looking for open release pull requests
2024-03-15T10:38:12.8225055Z ✔ found 0 open release pull requests.
2024-03-15T10:38:12.8226551Z ✔ Looking for snoozed release pull requests
2024-03-15T10:38:13.0852016Z ✔ found 0 snoozed release pull requests.
2024-03-15T10:38:13.0856589Z ❯ Looking up SHA for branch: main
2024-03-15T10:38:13.1969551Z ❯ SHA for branch: f8db56d9bd9dec2c2188676775c67edb8fc0e783
2024-03-15T10:38:13.1971778Z ❯ Looking up SHA for branch: release-please--branches--main--release-notes
2024-03-15T10:38:13.3092712Z ❯ SHA for branch: dbcb18d4d9f44b43459b2e3548a57a5e46fd2094
2024-03-15T10:38:13.3095234Z ❯ Updating branch release-please--branches--main--release-notes to f8db56d9bd9dec2c2188676775c67edb8fc0e783
2024-03-15T10:38:13.5397785Z ❯ Updated branch: release-please--branches--main--release-notes to f8db56d9bd9dec2c2188676775c67edb8fc0e783
2024-03-15T10:38:13.5400576Z ❯ Updated release-please--branches--main--release-notes to match main at f8db56d9bd9dec2c2188676775c67edb8fc0e783
2024-03-15T10:38:13.7083316Z ##[error]release-please failed: Invalid request.

"sha" wasn't supplied.
2024-03-15T10:38:13.7434844Z Cleaning up orphan processes
```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the provided GitHub Actions YAML and the release-please-action v3 entry point. Reproduce the workflow and trace the request made immediately after the release-notes branch is updated, using the supplied log as the checkpoint. Done means the action completes without the “sha” request error.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.