Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(build): add asset to github release #330

Merged
merged 1 commit into from
Feb 26, 2024
Merged

Conversation

svnv
Copy link
Member

@svnv svnv commented Feb 23, 2024

Ref. https://dintero.slack.com/archives/G7ESUNQ0Z/p1708678043060989

Change configuration for semantic-release. With these changes we

  • change order of npm and github plugins (not sure if needed but it matches the order of when they have an effect better)
  • add npm plugin configuration so that the tarball from npm pack is added to the dist folder
  • add github plugin configuration with an asset entry that takes all tarballs in the dist folder

See related example in the docs for the npm plugin here https://github.com/semantic-release/npm?tab=readme-ov-file#examples

Docs:

@svnv svnv requested a review from andersem February 23, 2024 10:04
@svnv svnv self-assigned this Feb 23, 2024
@svnv svnv requested a review from frodeaa as a code owner February 23, 2024 10:04
@svnv svnv force-pushed the fix-github-release-add-build branch from a5bab91 to 19b92b2 Compare February 23, 2024 10:07
@svnv svnv merged commit d0a1d20 into master Feb 26, 2024
1 check passed
@svnv svnv deleted the fix-github-release-add-build branch February 26, 2024 08:41
Copy link

🎉 This PR is included in version 0.7.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

svnv added a commit that referenced this pull request Feb 27, 2024
Fixes #331
Ref. #330
Rel. semantic-release/npm#535
Rel. https://github.com/Dintero/Dintero.Checkout.Web.SDK/actions/runs/8045967660/job/21972265552

The previous config change did not work as intended. The npm plugin for semantic release seems to be running twice and the .tgz is not present in the dist folder, and from the logs it does not even look like the package created contains the actual build files either. Instead of trying to make sense of the npm plugin we try using the exec plugin to run npm pack before the github plugin creates is release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants