Repository navigation
Conversation
A missing token used to surface as "Could not get unknown property 'SDK_REGISTRY_TOKEN'" and a public (pk.) token as an HTTP 403 during dependency resolution. Check the token in the settings scripts of the root and compose builds and point to where a secret token with the `DOWNLOADS:READ` scope can be created.
|
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
A missing token used to surface as "Could not get unknown property 'SDK_REGISTRY_TOKEN'" and a public (pk.) token as an HTTP 403 during dependency resolution. Check the token in the settings scripts of the root and compose builds and point to where a secret token with the
DOWNLOADS:READscope can be created.User impact (optional)
Pull request checklist:
@JvmOverloads,@file:JvmName, etc).make update-apito update generated api files, if there's public API changes, otherwise theverify-api-*CI steps might fail.check changelogCI step will fail.v10.[version]release branch fix / enhancement, merge it tomainfirstly and then port tov10.[version]release branch.PRs must be submitted under the terms of our Contributor License Agreement CLA.