semantic-release / semantic-release/github

Assets not uploaded / detected ? May my configuration is wrong ?

Open
#846 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
534
Forks
150
Avg merge
1m
Merged PRs (30d)
3

Description

Here is my configuration,

{
 "branches": ["main"],
 "plugins": [
 "@semantic-release/commit-analyzer",
 "@semantic-release/release-notes-generator",
 [
 "@semantic-release/github",
 {
 "assets": [
 { "path": "dist" }
 ]
 }
 ],
 "@semantic-release/github"
 ],
 "publish": ["@semantic-release/github"],
 "verifyConditions": ["@semantic-release/github"],
 "success": false,
 "fail": false,
 "npmPublish": false
}

What's wrong with this ?

image

Here is my workflow

 release:
 permissions:
 contents: write
 issues: write
 pull-requests: write
 needs:
 - macos-build
 runs-on: ubuntu-latest
 steps:
 - name: Checkout
 uses: actions/checkout@v4
 - name: Download binaries
 uses: actions/download-artifact@v4
 with:
 path: dist

 - run: find .
 - uses: actions/setup-node@v4
 with:
 node-version: latest

 - name: "configure semantic-release"
 run: npm install -D semantic-release @semantic-release/github

 - name: Semantic Release
 uses: cycjimmy/semantic-release-action@v4
 env:
 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

And i confirm I got file in my dist directory.

Run find .
.
./README.md
./dist
./dist/iPingTray.dmg
./dist/iPingTray.dmg/iPingTray.dmg

Do you know why ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the semantic-release configuration and the release workflow, especially the @semantic-release/github assets setting and the actions/download-artifact step. Inspect the reported find . output and dist paths first; done means determining why the existing dist files are not detected or uploaded as release assets.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.