Open barjin opened 7 months ago
Ooooof, good catch. I'd say best bet is to merge the versioned docs into the release flow, but this can definitely be an issue in the future too... For simplicity i think we can just use the retry step we use for deploys to make it try to git pull, push several times
Yeah, unfortunately, we need the version_docs
to run conditionally (only on major
/ minor
releases, not patch
). The retry step we use for deploys
sounds - although still a bit hacky - like what we need right now, do you have a link for that pls?
Its the same step we use in I think docker cis on the docker repo to see if the module versions are published to npm yet. I can take a look at pr-ing this fix this week 👀
I mean, if you know where to look, it would be nice if you could 🙏🏽 No worries if you don't find the time, it's quite low-prio and I'll revolve to it sooner or later :)
We currently use workflow dispatch from the
release
job to update the Docker build settings (here).The issue is that the workflow dispatch doesn't wait for the workflow to finish, creating a race condition with the next job in the original workflow (
version_docs
)Both
version_docs
andcrawlee-docker-image-bump
are pushing into themaster
branch in this repo, causing race conditions (git
won't push on a branch that got new commits since the last pull - causing either of the two jobs to fail).For better reproducibility and less hassle - perhaps we can use something like https://github.com/marketplace/actions/trigger-workflow-and-wait to wait on the workflow-dispatch until it's done... and only then run the
version_docs
job?cc @vladfrangu