Phil Brown
Phil Brown
Was able to work around this by blanking out the `GITHUB_TOKEN`... ```shell GITHUB_TOKEN="" yarn set version 1.22.19 ```
After having a look in https://github.com/palantir/bulldozer/blob/develop/bulldozer/signals.go#L52, I can see that this is simply not possible without significant refactoring 😢 Consider this a wishful feature request
Totally broken with Python 3.12. The minimum version of Ansible supporting that is 2.16. See https://github.com/ansible/ansible/issues/81946 and the [support matrix](https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix)
Duplicate of #5206
This is quite frustrating. Getting non-stop build warnings for a .Net 5 project... > [NU1701] Package 'Microsoft.AspNet.WebApi.Client 4.0.20710' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the...
How about you guys cut a release with [this commit](https://github.com/Cyber-Duck/laravel-excel/commit/e2d30c4a59f510b6715f886d5abfbb7537e396c7) in it? That or deprecate a dead project
> If you want you can open a pull request for this It's not in my interests to do so. I'll just keep using the main project's README no matter...