dspy: changelog & breaking changes

Auto-tracked from github.com/stanfordnlp/dspy. Updated Jul 06, 2026.

3.3.0b1

2026-05-28
âš  Breaking changes
  • Try out the typed return path with dspy.context(experimental=True), and the public migration plan explains the staged transition for custom LM and adapter authors.
  • See the full plan here
  • The base install is lighter: numpy is now optional via dspynumpy, and direct dependencies on asyncer, xxhash, and typeguard were removed in favor of standard-library paths.
  • Users can move to the current GEPA DSPy integration in this beta. The breaking changes below call out the result-shape changes for code that inspects detailed GEPA outputs.
  • Breaking Changes
  • numpy is no longer installed with base dspy. Features that need NumPy now require the numpy extra

3.2.1

2026-05-05
âš  Breaking changes
  • Removed the upper bound on litellm. ()
  • Removed an unused setup-node step from the docs push workflow. ()

3.2.0

2026-04-21
âš  Breaking changes
  • remove code corruption in ProgramOfThought._parse_code by @adityasingh2400 ()
  • Deprecation warning for prefix, format, and parser kwargs in InputField/OutputField by @MaximeRivest ()
  • Move model capability checks to BaseLM to remove litellm from adapters by @MaximeRivest ()
  • remove n=5 assumption from modules tutorial example by @MaximeRivest ()
  • remove broken BetterTogether tutorial links by @isaacbmiller ()
  • docs Remove misleading confidence field from Classification example by @xieyj17 ()

3.1.3

2026-02-05
âš  Breaking changes
  • no longer get stuck on imports
  • Temporarily remove the GEPA tool optimization doc
  • Remove enable_tool_optimization feature

3.1.2

2026-01-19

✓ No breaking changes detected — looks safe to upgrade.

3.1.1

2026-01-19
âš  Breaking changes
  • Change FinalAnswerResult to FinalOutput and remove RLM __call
  • Remove overly permissive read permissions and add strict allow

3.1.0

2026-01-06
âš  Breaking changes
  • Remove unused notebook python file

3.1.0b1

2025-11-18
âš  Breaking changes
  • Remove unused notebook python file
Get breaking-change alerts for YOUR stack

Drop your email + the libraries you use. We'll alert you when one ships a breaking change — before it breaks your deploy. Free.

⚡ Want an alert the moment your stack breaks — not a weekly digest? ChangeRadar Pro adds instant alerts + unlimited libraries + AI migration steps.Go Pro — $9/mo

Related breaking-change trackers