Installation failed about mastodon-bot HOT 25 CLOSED

uhh ... let me find it ...
@yogthos this should work https://github.com/yogthos/mastodon-bot/blob/master/RELEASING.md#stable-release-should-be-done-from-master

from mastodon-bot.

Does the problem still exist?

In meantime we try out the installation process in a docker and test: https://gitlab.com/yogthos/mastodon-bot/-/merge_requests/9

We use debian buster for our tests .. but this should be comparable to ubuntu20.04 ...

Sorry for a very late reply, didn't get the time to try it, and now I can confirm it works! Thanks for your efforts!

from mastodon-bot.

I've bumped up deasync to 0.1.20, that might fix the issue.

from mastodon-bot.

I've bumped up deasync to 0.1.20, that might fix the issue.

Thank you so much, just so you know, the npm version still remain the same

from mastodon-bot.

@jerger what do we do again to trigger a rebuild :)

from mastodon-bot.

Hmm, it builds for me locally but we get an error with CI, did I miss a step there? :)

from mastodon-bot.

Okay, will have a look at it

from mastodon-bot.

thanks, maybe we could add a release script that does all the things like testing, bumping up the version, tagging, in order

from mastodon-bot.

the issue in our build script is

failed to run function: shadow.cljs.build-report/-main
...
NoSuchFileException: .shadow-cljs/release-snapshots/app/latest/main.js

seems shadow-cljs build-report has an issue ... releases are maybe not located at snapshot?

https://github.com/yogthos/mastodon-bot/runs/1364722777?check_suite_focus=true

from mastodon-bot.

Yeah I noticed that too, but we haven't changed anything with shadow config though, wonder why that broke all of a sudden.

from mastodon-bot.

may I fix this directly on master?

from mastodon-bot.

yeah definitely :)

from mastodon-bot.

correlated with thheller/shadow-cljs#475

from mastodon-bot.

@yogthos Seems I'm not allowed to push tags. Can u create 1.0.6 at origin/master ?

from mastodon-bot.

oh sure thing, and let me update your permissions for the future

from mastodon-bot.

one more try using 1.0.8 ?

from mastodon-bot.

ok going now, and can't see how you add access to push tags unfortunately

from mastodon-bot.

hmm do we have to push to NPM separately, still looks like the old version there.

from mastodon-bot.

np - hopefully now fixed the last issue. Pls tag 1.0.9 if you're back

Unfortunately I know no nice way for having a smarter roundtrip on programming ci :-(

from mastodon-bot.

no - the last step (uploading to npm) used the wrong base dir

from mastodon-bot.

Tried 1.0.9, but doesn't look like it made it either. Seems like it doesn't like the url is off Not Found - PUT https://registry.npmjs.org/mastodon-bot - Not found, looks like it should be https://www.npmjs.com/package/mastodon-bot

from mastodon-bot.

any idea how to configure your url ? As we do not configure any url outside of just using npm ...

from mastodon-bot.

Tried: e4cd6f2
But did not find any hint, which url exactly to take ...

from mastodon-bot.

Hmm, it doesn't seem like it should need to go in package.json. I looked here, but don't see anything specific about the URL either.

from mastodon-bot.

Does the problem still exist?

In meantime we try out the installation process in a docker and test: https://gitlab.com/yogthos/mastodon-bot/-/merge_requests/9

We use debian buster for our tests .. but this should be comparable to ubuntu20.04 ...

from mastodon-bot.