Gábor Csárdi

> This might work but I get tons of block messages from our SIEM. (I am not the user of the package in this case) Is it possible to configure...

Should be fixed in the next release, happening later today.

Yes it is indeed intentional behavior. However, I think the se case is important enough to support this optionally. I am thinking that pkgdepends should consider a character vector for...

First I would check if the PAT works instead of the username and password. E.g. put the PAT in the git credential store. (Or put the PAT in the `GITHUB_PAT_DEV_AZURE_COM`...

For the record, we should use `CURLOPT_HTTPAUTH ` with `CURLAUTH_ANY`, and `CURLOPT_USERNAME` and `CURLOPT_PASSWORD`.

The drawback of this is that sometimes the reason for failure is botched packages installation, and we would save a botched cache, that will be potentially picked up across all...

> Or do you mean that a bad package is installed successfully but during package checking, it fails? In this situation, the bad package would be cached for future restores....

> Will request a review when the PR is stable. Thank you! I wonder if it was better and easier to implement this is in pak itself.

> Update to use actions/cache@v4 as it now has a save-always: flag. Related: https://github.com/actions/cache/commit/b1378c8403e6779ec61a229f419bc68c0e118f02 Oh, that is awesome!

Thank you, and sorry for the long wait!