Skip to content

fix(ci): make publishing-check resolve only what was just published #110

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.

Sign up for GitHub

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

Merged
projectdelta6 merged 1 commit into from
Aug 21, 2026
Merged

fix(ci): make publishing-check resolve only what was just published #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion publishing-check/settings.gradle.kts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,13 @@
// with its own resolution rules and cannot affect how the library itself resolves anything.
dependencyResolutionManagement {
repositories {
// mavenLocal FIRST and no JitPack repository, deliberately. The point of this check is what
// the toolbox *just published locally*. With JitPack in the list, a module that silently
// failed to publish could resolve from the released artifact of the same version instead
// and the check would pass having tested the wrong thing entirely.
mavenLocal()
google()
mavenCentral()
maven { url = uri("https://jitpack.io") }
}
}

Expand Down
Loading