fix(deps): update dependency thinc to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
thinc	^8.0.10 -> ^9.0.0

---

Release Notes

explosion/thinc (thinc)

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0: : better learning rate schedules, integration of thinc-apple-ops

Compare Source

The main new feature of Thinc v9 is the support for learning rate schedules that can take the training dynamics into account. For example, the new plateau.v1 schedule scales the learning rate when no progress has been found after a given number of evaluation steps. Another visible change is that AppleOps is now part of Thinc, so it is not necessary anymore to install thinc-apple-ops to use the AMX units on Apple Silicon.

✨ New features and improvements

• Learning rate schedules can now take the training step as well as an arbitrary set of keyword arguments. This makes it possible to pass information such a the parameter name and last evaluation score to determine the learning rate (#​804).
• Added the plateau.v1 schedule (#​842). This schedule scales the learning rate if training was found to be stagnant for a given period.
• The functionality of thinc-apple-ops is integrated into Thinc (#​927). Starting with this version of Thinc, it is not necessary anymore to install thinc-apple-ops.

🔴 Bug fixes

• Fix the use of thread-local storage (#​917).

⚠️ Backwards incompatibilities

• Thinc v9.0.0 only support Python 3.9 and later.
• Schedules are not generators anymore, but implementations of the Schedule class (#​804).
• thinc.backends.linalg has been removed (#​742). The same functionality is provided by implementations in BLAS that are better tested and more performant.
• thinc.extra.search has been removed (#​743). The beam search functionality in this module was strongly coupled to the spaCy transition parser and has therefore moved to spaCy in v4.

👥 Contributors

@​adrianeboyd, @​danieldk, @​honnibal, @​ines, @​kadarakos, @​shadeMe, @​svlandeg

v8.3.2

Compare Source

v8.3.1

Compare Source

v8.3.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: services/rule/poetry.lock

Updating dependencies
Resolving dependencies...


Because no versions of spacy match >3.7.5,<3.7.6a0 || >3.7.6a0,<3.8.0.dev0 || >3.8.0.dev0,<3.8.2 || >3.8.2,<4.0.0
 and spacy (3.7.6a0) depends on thinc (>=8.2.2,<8.3.0), spacy (>3.7.5,<3.8.0.dev0 || >3.8.0.dev0,<3.8.2 || >3.8.2,<4.0.0) requires thinc (>=8.2.2,<8.3.0).
And because spacy (3.8.0.dev0) depends on thinc (>=8.2.2,<8.3.0), spacy (>3.7.5,<3.8.2 || >3.8.2,<4.0.0) requires thinc (>=8.2.2,<8.3.0).
And because spacy (3.8.2) depends on thinc (>=8.3.0,<8.4.0)
 and spacy (3.7.5) depends on thinc (>=8.2.2,<8.3.0), spacy (>=3.7.5,<4.0.0) requires thinc (>=8.2.2,<8.4.0).
So, because rule-service depends on both spacy (^3.7.5) and thinc (^9.0.0), version solving failed.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud