chore(ci): add automatic release workflow for generic Actors #380
Conversation
github-actions
bot
added
the
t-tooling
| version: | ||
| description: Version to build | ||
| type: string | ||
| required: true | ||
| default: '3.0' |
There was a problem hiding this comment.
how does this work? some of the scrapers are on a lower version since they are newer, e.g. playwright and jsdom
also can this be used to trigger the development build of all of them at once?
There was a problem hiding this comment.
some of the scrapers are on a lower version since they are newer, e.g. playwright and jsdom
Ah, that's annoying, and I missed that. We can omit the version param altogether if we set the version right in the .apify/actor.json file. Right now, there's just a bunch of top-level apify.json files.
also can this be used to trigger the development build of all of them at once?
I don't see why not, even though we'll need to make sure all the development versions match.
Thinking about it now, it might be better to replace the build-tag and version options with a "build type" choice (picker with latest / beta / canary or something similar) and have the logic in the action internally. We might want to match all the Actor versions on the platform, so the implementation is easier, but I'm not sure about the implications of this.
Co-authored-by: Jan Buchar <jan.buchar@apify.com>
Fixes the missing pieces from #380 . Fixes the Camoufox scraper internals and dependencies.
Adds a manual-dispatch CI workflow for running generic Actor builds on Apify.