Tests against a matrix of supported flagsmith sdk versions ?

Open Beginner friendly
#38 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd, testing-qa

Research direction

Start with the pytest workflow and compare its current Python/version jobs with the matrix used in the Python SDK repository. Add the floor version 5.5.0, each supported minor through the latest version, and the locked version 6.2.0 as the Flagsmith axis. The existing version-gated tests should remain unchanged, and the workflow should pass across every matrix entry.

Written by the indexing model from the issue text.

Description

CI currently tests the locked flagsmith version (6.2.0) across all Python versions, plus a single job pinning the floor (5.5.0).

Add a flagsmith version axis to the pytest workflow, analogous to the matrix in the Python SDK repo, e.g. floor (5.5.0), each minor up to latest, and the lock, so signature drift in any supported version fails CI instead of surfacing at runtime.

Version-gated tests (engine reasons, >=6.2) already skip below their required version, so the matrix needs no test changes.

Dominant language
Python
Stars
6
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-openfeature-provider-python

All issues in Flagsmith/flagsmith-openfeature-provider-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.