Are you aware of any current issues with Yarn? ```> Could not resolve all files for configuratio...

# javascript

[CLOVIS]

Are you aware of any current issues with Yarn?

> Could not resolve all files for configuration ':detachedConfiguration2'.
   > Could not resolve com.yarnpkg:yarn:1.22.17.
     Required by:
         project :
      > Could not resolve com.yarnpkg:yarn:1.22.17.
         > Could not get resource '<https://github.com/yarnpkg/yarn/releases/download/v1.22.17/yarn-v1.22.17.tar.gz>'.
            > Could not HEAD '<https://objects.githubusercontent.com/github-production-release-asset-2e65be/49970642/9b940159-ba7f-49ac-a9d6-f989acd4d92e?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=[MASKED]&X-Amz-Date=20231122T092444Z&X-Amz-Expires=300&X-Amz-Signature=[MASKED]&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=49970642&response-content-disposition=attachment%3B%20filename%3Dyarn-v1.22.17.tar.gz&response-content-type=application%2Foctet-stream>'. Received status code 401 from server: Unauthorized

[Matt Nelson]

Yup, CI failing for me too.

https://github.com/05nelsonm/kmp-tor-binary/actions/runs/6955601424/job/18924892406?pr=127#step:8:54

[Rafał Kuźmiński]

Same here, today it started failing on CI

[CLOVIS]

Are you seeing it fail on other platforms as well? This seems oddly similar: https://gitlab.com/opensavvy/playgrounds/gradle/-/jobs/5594089585#L41

[turansky]

Yarn 1.22.21 (with security update) works fine.

Configuration example