This repository was archived by the owner on Jan 28, 2026. It is now read-only.
Use dependency-groups for dev dependencies#47
Merged
Conversation
leszek-bq
approved these changes
Jan 26, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR uses the
dependency-groupsblock for dev dependencies (best-practice), rather thanproject.optional-dependencies.uvautomatically installs dev dependencies in thedependency-groupsblock, which simplifies workflows/instructions for setting up the project. Additionally, usingproject.optional-dependenciesmeant that we were building a user-facing group calledaurora-dsql-sqlalchemy[test]which shouldn't really be exposed given these are intended as internal dependencies only.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.