Skip to content
New issue

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

Make test-release.sh script check that artifacts have synced to Maven #812

Merged
merged 1 commit into from Jun 30, 2019

Conversation

@olafurpg
Copy link
Member

commented Jun 30, 2019

Previously, we used the -r sonatype:public resolver by default which
passed even if the artifacts hadn't synced t Maven Centra. This resulted
in many users getting resolution errors if they updated Metals right
after the release announcement (which is easy to do with VS Code
auto-update).

Previously, we used the `-r sonatype:public` resolver by default which
passed even if the artifacts hadn't synced t Maven Centra. This resulted
in many users getting resolution errors if they updated Metals right
after the release announcement (which is easy to do with VS Code
auto-update).
@gabro
gabro approved these changes Jun 30, 2019
@gabro gabro merged commit c146585 into scalameta:master Jun 30, 2019
3 checks passed
3 checks passed
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
scalameta.metals Build #20190630.5 succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.