dependency-submission triggered by tag on default branch does not update dependency results for repository
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 117
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 11
Description
### Current Behavior
A release is likely to be built of a tag which points to a commit on main
> Submitted dependency-graph-reports/release-release.json: The snapshot was accepted, but it is not for the default branch. It will not update dependency results for the repository.
minimal details of workflow,
### Expected Behavior
submission to a ref that points to a commit in the default branch should work.
### Context (optional)
_No response_
### Steps to Reproduce
obviously you'll have to add some actual gradle build steps, but it's not significant in this issue I think.
```yml
on:
push:
tags:
- "v*.*.*"
jobs:
release:
runs-on: ubuntu-latest
timeout-minutes: 5
permissions:
contents: write
packages: write
- uses: actions/checkout@v4
with:
ref: ${{ github.ref }}
- ...
- uses: gradle/actions/dependency-submission@v3
```
### Gradle version
8.7
### Build scan URL (optional)
_No response_
### Your Environment (optional)
checkout peformed differently than normal due to https://github.com/actions/checkout/issues/882
I'm not certain whether or not the dependency report should really be used on every build of the default branch vs an actual release. I guess for now it'll have to be every build of the default branch
Contributor guide
Research direction
Start with the tag-triggered workflow shown in the issue and the gradle/actions dependency-submission action entry point. Reproduce a release tag pointing to a default-branch commit and inspect why the submitted snapshot is rejected as not being for the default branch. Done means the dependency results update for the repository when the report is submitted from that release workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100