Commit graph

11 commits

Author SHA1 Message Date
jem
eec4c0e4ba add stable & unstable build options 2020-07-13 18:37:05 +02:00
jem
3a674288e4 remove dry run 2020-07-13 18:35:19 +02:00
jem
4decc91db3 Merge branch 'master' into improve_build 2020-07-13 18:35:03 +02:00
jem
e84079fb3d going to separate stable & unstable build 2020-07-13 18:31:18 +02:00
Arnout Engelen
4f21e40f73
Publish the target directory without creating our own tarball
This way 'npm publish' works and the package correctly has the
resources in a '/package' directory inside the tarball.

Tested by publishing locally, indeed the README is now correctly
shown at https://www.npmjs.com/package/mastodon-bot/v/1.0.1-test-raboof-3

Will release 1.0.2 from master after merging
2020-07-09 16:42:11 +02:00
Arnout Engelen
bdd6da6406
npm package tgz should contain a single folder
the npm package tgz should contain a single folder containing the package.json
and other resources. See https://docs.npmjs.com/cli/publish.

I suspect this is also the reason the README cannot be found
for https://www.npmjs.com/package/mastodon-bot/v/1.0.1
2020-07-09 09:36:31 +02:00
jem
be5703273c add npm-publish 2020-06-29 20:27:01 +02:00
jem
9a856e2cdc add shasum & allow 0.0.0-sth tags 2020-06-29 20:08:45 +02:00
jem
1b43d0ecda fix format 2020-06-29 19:42:44 +02:00
jem
43497f4cd3 maybe executable flag is also important to release artefact? 2020-06-29 18:48:47 +02:00
jem
43be60f8e4 found no way to do a release without tag 2020-06-29 18:28:09 +02:00
Renamed from .github/workflows/release-dev.yml (Browse further)