Add Dependabot for LiquidJava dependencies - #1
Merged
Merged
Conversation
Opens a PR whenever a new io.github.liquid-java artifact is published, so version bumps cascade across repos without manual updates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rcosta358
approved these changes
Sep 30, 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
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.
Description
Adds
.github/dependabot.ymlso that when a newio.github.liquid-javaartifact (api, verifier, fsm) is published to Maven Central, Dependabot opens a PR here bumping it. All LiquidJava artifacts are grouped, so one release produces one PR per repo.Part of the same setup in liquidjava, liquidjava-fsm, liquidjava-mcp and vscode-liquidjava, replacing manual version bumps after each release.
Only LiquidJava artifacts are tracked; other dependencies are unaffected.
🤖 Generated with Claude Code