8000 Automatically publish to npm · Issue #66 · vercel/satori · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Automatically publish to npm #66

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

Closed
styfle opened this issue Jun 3, 2022 · 3 comments · Fixed by #350
Closed

Automatically publish to npm #66

styfle opened this issue Jun 3, 2022 · 3 comments · Fixed by #350
Labels
enhancement New feature or request released

Comments

@styfle
Copy link
Member
styfle commented Jun 3, 2022

Perhaps we can use lerna or changesets

@styfle styfle added the enhancement New feature or request label Jun 3, 2022
@styfle styfle added this to the General Availability milestone Aug 3, 2022
shuding pushed a commit that referenced this issue Jan 9, 2023
@github-actions
8000 Copy link
github-actions bot commented Jan 9, 2023

🎉 This issue has been resolved in version 0.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@pauliesnug
Copy link

@styfle Is it possible to use semantic-release to add GitHub artifact attestations to the npm release?

@styfle
Copy link
Member Author
styfle commented May 12, 2025

This might work:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0