Publishing on OSX Big Sur about skpm HOT 7 CLOSED

Is there any workaround?

I've been publishing plug-in updates manually. Process (change 2.0.0 to correct version number):

• Update version in package.json (or manifest.json if you have version number there)
• Build plugin, commit all changes (as usual before publishing)
• Add tag: git add tag 2.0.0 -m "v2.0.0"
• Push tag to GitHub: git push origin 2.0.0
• Go to releases (https://github.com/{username}/{repo}/releases), create new release:
  • Select tag "2.0.0"
  • Title: "v2.0.0"
  • Description: "Publish 2.0.0 release :rocket:"
  • Drag your plugin-name.sketchplugin to "Attach binaries" field. I'm using Finder and Safari, which automatically zip it before uploading.
  • Publish release.
• Open .appcast.xml, copy first entry, change version number.
• Commit changes to .appcast.xml, push it to GitHub repo.

from skpm.

FTR, I’m seeing this too on Catalina, so definitely not a Big Sur issue.

I initially thought it might be an issue with Homebrew’s git version, but uninstalling it and using Apple’s default throws the same error 🤔

from skpm.

same here. Is there any workaround?

from skpm.

I think this problem is caused by a change in the output of npm version.

Here is a part that call npm version command, and assign trimmed stdout into tag variable. There are lots of code that replacing 'v' from the tag variable. These codes tell us that output of npm version was like 'vX.Y.Z'.

Unfortunately, I think the problem is caused by the removal of the 'v' character from the npm version output, so it no longer matches the name of the git tag.

from skpm.

looks like you're right, we should now add it if it's not there 🤔 (so 1.1.8 becomes v1.1.8 and matches the created tag). Want to send a PR?

from skpm.

@mathieudutour
I'm not very experienced with Node.js, so I need to learn how to debug. Could you tell me how to do that?

from skpm.

@macintoshhelper
I figured out how to develop skpm now. I will send a PR soon.

from skpm.