chore: bump apify ui components to an existing version

[vladfrangu]

In the time where I fixed the repo to be usable on windows and actually testing, it seems like the version expired (?) or was deleted. Either way, bumping its patch only (as it uses 0ver and any further bumps technically are major)

[B4nan]

hmm, this is so fragile, we should really make this package public so we can keep the versions. if the changes wouldnt be breaking for us, i wouldnt mind, but sometimes they are...

cc @jbartadev is this something your team can handle or can we somehow help/do it ourselves?

[vladfrangu]

Fun times ahead. Bumping this somehow broke dev completely, because ui-components's dependencies for some reason import apify/log down the chain, a module that was never intended for browsers from the looks of things... And the older version the master branch currently relies on doesn't exist anymore....

UPDATE 1: these cosmic rays need to stop, with the cached version I still have locally of ui-components, apify/log still comes through but DEV works!?

UPDATE 2: for some reason pinning it to a previous version made it work. This is...very fragile... we should ideally make these components either public or split them out of the private package

[jbartadev]

hmm, this is so fragile, we should really make this package public so we can keep the versions. if the changes wouldnt be breaking for us, i wouldnt mind, but sometimes they are...

cc @jbartadev is this something your team can handle or can we somehow help/do it ourselves?

@B4nan Yeah, let's make it public, it looks like it'll save us a lot of pain in the future. It'll require some dependencies removal from the package. We'll try to take a look at it ASAP.

[vladfrangu]

I'll merge this as is for now, looking forward to moving to the public components 🙏