question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot get the assets uploaded properly for a release

See original GitHub issue

Here is my semantic-release configuration in package.json:

  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    [
      "@semantic-release/github",
      {
        "assets": [
          "out"
        ]
      }
    ]
  ]

Upon a commit with the message: fix(ci): Message here I get the following output:

❯❯ phils :: nextjs-blog git(main) 16:12  .\node_modules\.bin\semantic-release --no-ci
[4:12:26 PM] [semantic-release] » i  Running semantic-release version 17.3.4
[4:12:26 PM] [semantic-release] » √  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "verifyConditions" from "@semantic-release/github"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "prepare" from "@semantic-release/npm"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "publish" from "@semantic-release/npm"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "publish" from "@semantic-release/github"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "addChannel" from "@semantic-release/npm"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "addChannel" from "@semantic-release/github"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "success" from "@semantic-release/github"
[4:12:26 PM] [semantic-release] » √  Loaded plugin "fail" from "@semantic-release/github"
[4:12:32 PM] [semantic-release] » √  Run automated release from branch main on repository https://github.com/pstephenson02/nextjs-blog.git
[4:12:34 PM] [semantic-release] » √  Allowed to push to the Git repository
[4:12:34 PM] [semantic-release] » i  Start step "verifyConditions" of plugin "@semantic-release/npm"
[4:12:34 PM] [semantic-release] » √  Completed step "verifyConditions" of plugin "@semantic-release/npm"
[4:12:34 PM] [semantic-release] » i  Start step "verifyConditions" of plugin "@semantic-release/github"
[4:12:34 PM] [semantic-release] [@semantic-release/github] » i  Verify GitHub authentication
[4:12:34 PM] [semantic-release] » √  Completed step "verifyConditions" of plugin "@semantic-release/github"
[4:12:34 PM] [semantic-release] » i  Found git tag v0.1.4 associated with version 0.1.4 on branch main
[4:12:34 PM] [semantic-release] » i  Found 1 commits since last release
[4:12:34 PM] [semantic-release] » i  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[4:12:34 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: fix(ci): Try a different glob
[4:12:34 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The release type for the commit is patch
[4:12:34 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analysis of 1 commits complete: patch release
[4:12:34 PM] [semantic-release] » √  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[4:12:34 PM] [semantic-release] » i  The next release version is 0.1.5
[4:12:34 PM] [semantic-release] » i  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[4:12:34 PM] [semantic-release] » √  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[4:12:34 PM] [semantic-release] » i  Start step "prepare" of plugin "@semantic-release/npm"
[4:12:34 PM] [semantic-release] [@semantic-release/npm] » i  Write version 0.1.5 to package.json in C:\Users\phils\Code\pstephenson02\nextjs-blog
v0.1.5
[4:12:35 PM] [semantic-release] » √  Completed step "prepare" of plugin "@semantic-release/npm"
[4:12:44 PM] [semantic-release] » √  Created tag v0.1.5
[4:12:44 PM] [semantic-release] » i  Start step "publish" of plugin "@semantic-release/npm"
[4:12:44 PM] [semantic-release] [@semantic-release/npm] » i  Skip publishing to npm registry as package.json's private property is true
[4:12:44 PM] [semantic-release] » √  Completed step "publish" of plugin "@semantic-release/npm"
[4:12:44 PM] [semantic-release] » i  Start step "publish" of plugin "@semantic-release/github"
[4:12:45 PM] [semantic-release] [@semantic-release/github] » i  Published GitHub release: https://github.com/pstephenson02/nextjs-blog/releases/tag/v0.1.5
[4:12:45 PM] [semantic-release] » √  Completed step "publish" of plugin "@semantic-release/github"
[4:12:45 PM] [semantic-release] » i  Start step "success" of plugin "@semantic-release/github"
[4:12:47 PM] [semantic-release] » √  Completed step "success" of plugin "@semantic-release/github"
[4:12:47 PM] [semantic-release] » √  Published release 0.1.5 on default channel

image

The release gets generated, but the assets (neither the .zip nor the .tar.gz) do not include the contents of the out directory.

I feel like I’m missing something really obvious here?

EDIT: Just to clarify, what I expect to happen is that all the files in the out directory get bundled into the .zip and .tar.gz files and uploaded with the release. I have also tried the glob out/**

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
gr2mcommented, Jan 20, 2021

I think semantic-release is logging its configuration when you run semantic-release withe the --debug flag, that’d have probably pointed you to the right direction.

0reactions
pstephenson02commented, Jan 21, 2021

@gr2m That’s ultimately how I tracked it down. Thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cannot upload github release asset through API
Wrong upload URL. The URL you use to upload assets is not the same one ou use for all other API calls. To...
Read more >
Unable to retry upload of a failed release asset #2648 - GitHub
Did you try that command? Usually, retrying uploading a corrupt asset should first delete an existing asset of the same name, which should ......
Read more >
Uploading Assets to App Store Connect - Apple Developer
You can upload parts of your asset concurrently and in any order to improve performance. If one part doesn't upload correctly, you can...
Read more >
Fix common Google Ads Editor errors
For example, this error could be caused by trying to upload message assets, which are no longer supported. Remove the deprecated feature, such...
Read more >
Releases - GitLab Documentation
When you delete a release, its assets are also deleted. However, the associated Git tag is not deleted. Prerequisites: You must have at...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found