Daniel Kraus

One can abuse [secrets](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to clear the cache via the UI, i.e. without editing the workflow file. For instance, create a secret using the key `CACHE_VERSION` and as value a...

> 2 years in, still no manual cache control... because the team who built this clearly never uses it in their own work. > > allow user to clear cache...

Same here, although my SSH key is under `~/.ssh/id_rsa`: ``` [ERROR] [ERROR] [ERROR] [ERROR] ************************************ [ERROR] Could not execute the release plugin [ERROR] ************************************ [ERROR] [ERROR] [ERROR] There was an...

Thanks for the fast response, Daniel. I forgot I was using a passphrase for my SSH key, which caused the error. Although I wasn't able to make it work by...

OK, thx for pointing to `PropertiesMapper`. Will have a look at it.

A little workaround: As a MacTex user, it's quite easy to [handle multiple TeX Live versions](http://www.tug.org/mactex/multipletexdistributions.html): Tex Live Utility > Configure > Change Default TeX Live version… (which allows you...

@kchaksuvej you mean like a command-line interface (CLI) for scripting? For example: ```text $ pdfzw --mode=single --copy --infix='-modified' my-document.pdf ``` If that is what you mean, no, it doesn't exist...

> **Warning** > Added `merge-ready` only to run full build.

Related: https://github.com/google/jimfs/issues/204

As already mentioned in #140, I think code names are somewhat optional and they probably only appear in major releases. IMHO the changelog should focus on the version number: ```...