meissa
/
mastodon-bot
Archived
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
278 Commits
1 Branch
6 Tags
727 KiB
master
1.10.11
1.10.10
1.10.9
1.10.8
1.10.7
1.10.5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5d0f6fbb97'
${ noResults }
Commit Graph

38 Commits (5d0f6fbb97bb333981b61268b036d2ce1aceaed5)

Author SHA1 Message Date
Michael Jerger 8c97d8bdf0 improve prerelease ci 3 years ago
jem 6465434dfa minor fix 3 years ago
jem 113bd080ac fix version for publishing 3 years ago
jem 85406aab99 version bump 3 years ago
dmitri.sotnikov@gmail.com 6bd61ccd2f bumped up version 4 years ago
dmitri.sotnikov@gmail.com 10cdbb0a7e 1.10.1 4 years ago
dmitri.sotnikov@gmail.com 1658e4fb00 fixed package.json 4 years ago
dmitri.sotnikov@gmail.com 330d9739c2 1.10.0 4 years ago
Dmitri Sotnikov adfef0e663
updated repository url 4 years ago
jem e4cd6f2f2f configuring the npm reg - but unsure about the url to use. 4 years ago
jem 8df1214255 releasing 4 years ago
jem 2a37e55158 releasing 4 years ago
jem 2feca1f23e version bump 4 years ago
jem 9b688a23cb releasing 4 years ago
dmitri.sotnikov@gmail.com 5414e01048 releasing 4 years ago
Dmitri Sotnikov 03a4c950cf
update deasync to 0.1.20 4 years ago
dmitri.sotnikov@gmail.com 96ececd255 bumped up version 4 years ago
dmitri.sotnikov@gmail.com e7b0ed233e bumped up package.json version 4 years ago
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
 4 years ago
dmitri.sotnikov@gmail.com 5f23a98920 bumped up package.json version 4 years ago
jem 57376d2e15 increase version for improved release publishing ci 4 years ago
dmitri.sotnikov@gmail.com 27c99a7d55 bumped up version for release 4 years ago
jem b231fc5209 works :-) 4 years ago
jem 09046c0dee next try to publish 4 years ago
jem 49fe78dc06 prepare for publishing on npm 4 years ago
jem ceaf1a2034 maybe files have also to be adjusted in package.json? 4 years ago
jem 64cea0fea7 fix package.json 4 years ago
Arnout Engelen 9c80c4cab0
Release 0.0.2 4 years ago
Arnout Engelen 7f992e9d73
Add filters so 'npm pack' and publish contains just enough 4 years ago
Arnout Engelen 043f1e0fd3 Remove separate main.cljs, install to PATH 
https://docs.npmjs.com/files/package.json#bin
 4 years ago
dmitri.sotnikov@gmail.com 820cd2be82 added shadow-cljs compilation to generate a js artifact 4 years ago
Arnout Engelen ea7c057c11 Add a unit test 
Splitting up the project in core/main/test
 4 years ago
dmitri.sotnikov@gmail.com d79b9fa5c3 bumped up dependencies 5 years ago
Dmitri Sotnikov 8c004bd876 switched to use request module instead of curl to resolve urls 6 years ago
dmitri.sotnikov@gmail.com 1f411891a8 added RSS support 6 years ago
dmitri.sotnikov@gmail.com f67f55c858 added tumblr support 6 years ago
AJ Jordan 8bf710dd61
Declare Lumo as a dependency 
This means that we always have the right version, regardless of what's
in the global environment. Note that npm scripts (including `npm
start`) automatically prepend `./node_modules/.bin` to $PATH, which is
how this works.

See also http://module.party
 6 years ago
dmitri.sotnikov@gmail.com 75b679a533 initial commit 6 years ago