unable to access 'https://github.com/***-dev/js/': The requested URL returned error: 503

unable to access 'https://github.com/***-dev/js/': The requested URL returned error: 503

Type 'string | { r: `0x${string}`; s: `0x${string}`; yParity: number; }' is not assignable to type 'string | Uint8Array<ArrayBufferLike> | { r: bigint; s: bigint; yParity: number; }'.

Type 'Partial<{ prevOwner: string; newOwner: string; }>' is not assignable to type 'Readonly<{ prevOwner?: undefined; newOwner?: undefined; }>'.

Type 'Partial<{ prevOwner: string; newOwner: string; }>' is not assignable to type 'Readonly<{ prevOwner?: undefined; newOwner?: undefined; }>'.

Type 'Partial<{ platformFeeRecipient: string; }>' is not assignable to type 'Readonly<{ platformFeeRecipient?: undefined; }>'.

Type 'Partial<{ recipient: string; }>' is not assignable to type 'Readonly<{ recipient?: undefined; }>'.

Type 'Partial<{ newRoyaltyRecipient: string; }>' is not assignable to type 'Readonly<{ newRoyaltyRecipient?: undefined; }>'.

Type 'Partial<{ tokenId: bigint; royaltyRecipient: string; }>' is not assignable to type 'Readonly<{ tokenId?: undefined; royaltyRecipient?: undefined; }>'.

Type 'Partial<{ previousAddress: string; newAddress: string; }>' is not assignable to type 'Readonly<{ previousAddress?: undefined; newAddress?: undefined; }>'.

Type 'Partial<{ tokenAddress: string; tokenOwner: string; recipient: string; }>' is not assignable to type 'Readonly<{ tokenAddress?: undefined; tokenOwner?: undefined; recipient?: undefined; }>'.

Type 'Partial<{ claimer: string; receiver: string; tokenId: bigint; }>' is not assignable to type 'Readonly<{ claimer?: undefined; receiver?: undefined; tokenId?: undefined; }>'.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element