Bassem Dghaidi
Bassem Dghaidi
A couple of weeks, tops. The PR with the change is being merged as we speak.
@enescakir thank you for your contribution. We will be looking into this after we finish the roll-out of the new service
> There will be no need to offer backward compatibility as the new service will be rolled out to all repositories by February 13th 2025. **I'm afraid this statement is...
> I'm open to using either `rust-lang/setup-rust` or `actions/setup-rust`. However, `actions/setup-rust` might be the better choice since most individuals and organizations have already permitted the use of `actions/*` in their...
Apologies for the delay on this, we're actively investigating this with high urgency.
I created a test to investigate this behaviour: https://github.com/actions/upload-artifact/pull/754 I was not able to reproduce the problem you're referring to. Feel free to inspect the test, and try to run...
For extra clarity: - **v5** uses `@azure/[email protected]` which depends on `@azure/[email protected]` - **v6** uses `@azure/[email protected]` which uses `@azure/core-rest-pipeline` instead I was suspecting that this might be the cause of the...
> The 2nd request is not obviously “RFC-illegal” purely on syntax (headers are allowed), but it’s absolutely outside what many forward proxies accept for CONNECT Good callout 🤔 I need...