fix: Restrict docling library versions to resolve dependency issues + update mypy linting packages (backport #434)

[mergify]

docling-parse is automatically pulled in by docling as a dependency, and v3.0.0 of docling-parse contains breaking syntax changes that prevent our e2e builds in instructlab from succeeding. See issue in InstructLab here: instructlab/instructlab#2765

For now, we will pin docling-parse to the latest v2 release while we investigate how we can update the docling-parse syntax to use the new v3 syntax. We will also pin to docling<=2.8.3 because v2.10.0 was updated to use docling-parse>=3.0.0. See here: https://github.com/DS4SD/docling/releases/tag/v2.10.0 (Docling-parse v2 as default PDF backend)

Finally, mypy is experiencing issues with a breaking upstream change, too. By default, mypy pulls in the latest version of pydantic, which is unfortunately now incompatible with mypy as of its v2.10 release. See:

• Limited inference with union of callables and assignment to a union python/mypy#18191
• mypy type-checking issues affecting a Field's default value or default_factory after upgrade to 2.10 pydantic/pydantic#10950

To workaround this dependency issue, I pinned the related dependency, pydantic, to <=v2.9.2 in our tox.ini file. This will force our latest mypy to use a compatible pydantic. However, note that I did also pin mypy>=1.0,<1.14. I did this as a safety measure for when the mypy maintainers inevitably fix the issue in v1.14 or later.

---

This is an automatic backport of pull request #434 done by Mergify.

[mergify]

Cherry-pick of 2e00bb8 has failed:

On branch mergify/bp/release-v0.6/pr-434
Your branch is up to date with 'origin/release-v0.6'.

You are currently cherry-picking commit 2e00bb8.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   CHANGELOG.md

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both added:      .github/workflows/actionlint.yml
	both added:      .github/workflows/docs.yml
	both added:      .github/workflows/e2e-nvidia-l4-x1.yml
	both added:      .github/workflows/e2e-nvidia-l40s-x4.yml
	both added:      .github/workflows/e2e-nvidia-t4-x1.yml
	both added:      .github/workflows/lint.yml
	both added:      .github/workflows/pypi.yaml
	both added:      .github/workflows/spellcheck.yml
	both added:      .github/workflows/stale_bot.yml
	both added:      .github/workflows/test.yml
	both added:      .spellcheck-en-custom.txt
	both added:      README.md
	both added:      requirements-dev.txt
	both added:      requirements.txt
	both added:      src/instructlab/sdg/generate_data.py
	both added:      src/instructlab/sdg/utils/json.py
	both added:      tox.ini

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[jaideepr97]

@Mergifyio rebase

[mergify]

rebase

☑️ Nothing to do

Details

• any of:
  • #commits > 1 [📌 rebase requirement]
  • #commits-behind > 0 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]
• -closed [📌 rebase requirement]
• -conflict [📌 rebase requirement]
• queue-position = -1 [📌 rebase requirement]

[bbrowning]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[bbrowning]

@courtneypacheco I had to manually cherry-pick this on top of what mergify created - can you verify the changes look good?

[courtneypacheco]

Yes, the changes look good. Thank you!

[bbrowning]

Merged - thanks for the review!