Build workflow has been automatically disabled by GitHub

[AndrzejProchyra]

This is because the workflow has a schedule for a weekly build and GitHub disables scheduled builds "when no repository activity has happened in 60 days".

In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days. For information on re-enabling a disabled workflow, see Disabling and enabling a workflow.

(reference)

We therefore need to manually reenable the workflow so that builds happen. Unfortunately a development build release is currently only generated on a push event and can't be triggered manually (because of a condition in the main workflow).

Perhaps it would be best to move the scheduled build to a separate workflow too, so that the main one doesn't get automatically disabled...

[Ducasse]

Hi

In fact I do not know ;) if you have an idea or solution let me know. In general when I work on a book I push regularly and then this is ok that it goes in dormance mode. So this is why I did not worry much about it. I was a large work to migrate all the book to microdown and also to make sure that the build is kept working even when latex versions are not that compatible.

S

[AndrzejProchyra]

Hi Stéphane

I love these books and truly appreciate the work that has gone into them and the toolchain. But I am also eager to see the latest words beautifully rendered as a PDF book 🙂. Ideally, I would love to always have both a continuous build of the very latest state of the book and stable releases from tagged commits. This would let me and others point people at a "stable" version and the "very latest" version. It would also make it easier and more motivating to make contributions.

In the Spec 2 book in particular:

• I have the paperback copy and it seems to have been genrated from 28c96a1c897747c22e336168180cf8aabde8d897 in October last year but there is no tag on that commit
• The "latest" build (from commit 29aabdf553f6be445bea4b680feeab630990f167) is from last November but a number of corrections, etc, have been merged since then and it is not "obvious" how to build the corrected book

I enabled the build on my fork and triggered it manually. The PDF looks good!

So I think enabling the workflow here would be useful, and I could propose a small PR to separate out the scheduled workflow, if this would be helpful. Perhaps also a small PR to BookBuilderDashboard to enable triggering a pre-release build manually from here and the other book repos.