4d51d834ea
fix the npm publish dir
2020-11-06 19:14:11 +01:00
4769b838f4
remove the report upload
2020-11-06 19:03:13 +01:00
99ad3bfe36
remove report for our builds
2020-11-06 18:19:20 +01:00
5220d13ea1
unstable only works with tags atmo
2020-07-13 18:48:39 +02:00
eec4c0e4ba
add stable & unstable build options
2020-07-13 18:37:05 +02:00
3a674288e4
remove dry run
2020-07-13 18:35:19 +02:00
4decc91db3
Merge branch 'master' into improve_build
2020-07-13 18:35:03 +02:00
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
be5703273c
add npm-publish
2020-06-29 20:27:01 +02:00
87c5707e9c
next try
2020-06-29 20:12:14 +02:00
f4e9a44f37
fix PR test
2020-06-29 20:10:42 +02:00
9a856e2cdc
add shasum & allow 0.0.0-sth tags
2020-06-29 20:08:45 +02:00
1b43d0ecda
fix format
2020-06-29 19:42:44 +02:00
82d2a7b10f
test should work on every branch
2020-06-29 19:42:28 +02:00
0f0e380ff2
fix test PR workflow
2020-06-29 19:12:39 +02:00
43497f4cd3
maybe executable flag is also important to release artefact?
2020-06-29 18:48:47 +02:00
43be60f8e4
found no way to do a release without tag
2020-06-29 18:28:09 +02:00
a150b1faa9
there is no mkdir ??
2020-06-29 18:20:52 +02:00
507a83969e
no mor matrix for release
2020-06-29 18:13:55 +02:00
80681be786
try to fix run
2020-06-29 18:06:14 +02:00
dc7818e775
one more try #899
2020-06-29 17:58:40 +02:00
e2bf78f090
try #518 :-(
2020-06-29 17:51:30 +02:00
853d87a686
improve caching
2020-06-29 17:50:14 +02:00
43a077a641
separate uses & run steps
2020-06-29 17:42:28 +02:00
ba065753b2
add caching & use single wf & steps
2020-06-29 17:35:04 +02:00
8ceded6122
try #3
2020-06-29 13:40:34 +02:00
d6caab9d78
next try
2020-06-29 13:30:29 +02:00
929505b553
next try
2020-06-29 13:27:51 +02:00
f9f75a2324
next try ...
2020-06-29 13:18:27 +02:00
65d4c54bb6
try to express dev/prod release
2020-06-29 13:15:11 +02:00
b009b533b4
test package a release
2020-06-29 09:56:37 +02:00
c6187eb178
uff, no sharing between workflows?!
2020-06-29 09:26:28 +02:00
7d1f729bac
separate test & release
2020-06-29 09:23:59 +02:00
43b03b2740
rename
2020-06-29 09:23:46 +02:00
97b640e3b7
ci: install shadow as executable?
2020-06-27 15:47:02 +02:00
d25ff69725
ci: fix shadow-cljs install ?
2020-06-27 15:43:55 +02:00
d1f1850001
ci: remove caching
2020-06-27 15:39:00 +02:00
dd6f45b4ee
fix ci-cache
2020-06-27 15:35:33 +02:00
e63e76a9c2
fix ci issue
2020-06-27 15:34:36 +02:00
258c91128a
first try for automating builds
2020-06-27 15:29:02 +02:00
