search

changesets / action

661 stars 231 forks source link

Add a new input to do GitHub release without npm publishing #204

Open JounQin opened 2 years ago

JounQin commented 2 years ago

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

I recently met this problem again on releasing vscode-mdx which is not a npm package. 😂

See also #885

JounQin commented 2 years ago

cc @Andarist

openscript commented 1 year ago

Can changesets be used without npm by now?

khanisak commented 3 weeks ago

@openscript do you have the answer by now ?

schoenwaldnils commented 3 weeks ago

Had the same problem. I can't remember where I found it. But this was my solution:

- name: Create Release Pull Request
  id: changesets
  uses: changesets/action@v1
  with:
    title: 🚀 Release new version
    publish: npx @changesets/cli tag # this will create a new tag and a new release
khanisak commented 3 weeks ago

for anyone who came up to this issue, the solution for me is

  1. Mark your package or application with "private": true in package.json
  2. Add this property to .changeset/config.json file

    { "privatePackages": { "version": true, "tag": true } }

Then finally you can run npx @changesets/cli tag mentioned by @schoenwaldnils or npx @changeset/cli publish