Way to test SQLite 3.37 (and potentially other versions) in CI
Open
Nobody has claimed this yet.
ci
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 172
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Need to figure out a good pattern for testing this in CI too - it will currently skip the new tests if it doesn't have SQLite 3.37 or higher.
Originally posted by @simonw in https://github.com/simonw/sqlite-utils/issues/344#issuecomment-982076924
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No CI file or test path is named in the issue. Start by locating the repository's CI configuration and the tests currently skipped without SQLite 3.37 or higher; define a CI pattern that exercises those tests against SQLite 3.37 and potentially other versions, then verify the matrix runs the new tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- ci-cd, databases, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100