We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mentioned in the package.json is the dependency of: "com.google.external-dependency-manager": "1.2.178".
When looking at Google's archive, you can see that this version is not listed (jumping from 1.2.177 to 1.2.179): https://developers.google.com/unity/archive#external_dependency_manager_for_unity The version 1.2.178 seems to have been deprecated - although I'm not entirely sure why.
So the question is should this dependency be bumped to 1.2.179?
The text was updated successfully, but these errors were encountered:
Yes, we'll bump it for the next release.
Sorry, something went wrong.
If you're curious, this is why 1.2.178 was not included in the archive: googlesamples/unity-jar-resolver#672
The changes from 1.2.178 to 1.2.181 aren't major, but we'll still look into updating.
No branches or pull requests
Question
Mentioned in the package.json is the dependency of: "com.google.external-dependency-manager": "1.2.178".
When looking at Google's archive, you can see that this version is not listed (jumping from 1.2.177 to 1.2.179): https://developers.google.com/unity/archive#external_dependency_manager_for_unity
The version 1.2.178 seems to have been deprecated - although I'm not entirely sure why.
So the question is should this dependency be bumped to 1.2.179?
The text was updated successfully, but these errors were encountered: