Repository navigation
Resolve SeriouslyCommonLib from GitHub releases - #433
Merged
Merged
Conversation
Adds an Ivy repository pointing at SeriouslyCommonLib's GitHub releases (see Team488/SeriouslyCommonLib#694). The Azure feed stays for versions published before the move. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks
aschokking
approved these changes
Nov 7, 2026
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
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.
Why are we doing this?
SeriouslyCommonLib is moving off Azure DevOps (Team488/SeriouslyCommonLib#694). After that PR merges, every merge to SeriouslyCommonLib's
mainis published as a GitHub release (tag = version, e.g.20261107.193005) instead of to the Azure Artifacts Maven feed. This project needs to know where to find those new versions.Whats changing?
ivy { ... }repository that downloadsxbot.common:SeriouslyCommonLibjars straight from SeriouslyCommonLib's GitHub releases. No credentials needed.20260405.5) and older versions only exist there.SeriouslyCommonLibVersionis unchanged, so this is safe to merge before Migrate CI to GitHub Actions and release via GitHub releases SeriouslyCommonLib#694. The local../SeriouslyCommonLibcomposite-build setup is unaffected.Follow-up after Team488/SeriouslyCommonLib#694 merges
SeriouslyCommonLibVersionto a tag from https://github.com/Team488/SeriouslyCommonLib/releasesmaven { ... }block.Versions must be pinned exactly;
+/latest.releasedon't work against release URLs.Questions/notes for reviewers
The repository only serves the
xbot.commongroup (content { includeGroup ... }), so it doesn't slow down resolution of other dependencies.How this was tested
./gradlew dependencyInsight --dependency SeriouslyCommonLib --refresh-dependenciesstill resolvesxbot.common:SeriouslyCommonLib:20260405.5. It isn't on GitHub releases, so Gradle falls through to the Azure feed.ivyblock was verified in Migrate CI to GitHub Actions and release via GitHub releases SeriouslyCommonLib#694 against a release-style layout and against real GitHub release download redirects.🤖 Generated with Claude Code