feat: create GitHub releases on `changeset publish`
See original GitHub issueAffected Packages
@changesets/cli
Problem
We’re publishing to npm manually at https://github.com/mdx-js/eslint-mdx, and changeset publish
does not create GitHub releases automatically, this functionality is only available in changesets’ action
Proposed solution
https://github.com/changesets/action/blob/6a46d2c28377497e64763ba5f1faeabbd3d88c33/src/run.ts#L94
Move pushTags
and createReleases
into changeset publish
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Set up changesets in a GitHub repository - Cole Bemis
Initialize changesets yarn changeset init. Add a release script // package.json { "scripts": { "release": "yarn build && changeset publish" } }.
Read more >How To Automatically Generate A Helpful Changelog From ...
Creating a changelog is a usual task if a new software version is going to be released. It contains all the changes which...
Read more >Automatically generate and release a changelog using Node.js
In this tutorial, we'll explore a method for automatically generating and releasing a changelog that uses git hooks and Node.js.
Read more >README - semantic-release
Release steps ; Create Git tag. Create a Git tag corresponding to the new release version. ; Prepare. Prepare the release. ; Publish....
Read more >Migrating from Lerna to Changesets - Apollo Elements
We had a flaky CD setup via lerna and GitHub actions, which would often ... name: Release on: push: branches: - main jobs:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Or maybe we can do GitHub release on GitHub Action without npm publishing, how do you think?
I recently met this problem again on releasing
vscode-mdx
which is not a npm package. 😂cc @Andarist
changelog-github lives in this repo, so there is precedent for some github integration here, even if it might technically not be “core” (since it’s a plugin). 😄