Repository navigation
v1.0.0
First stable release of the bundle. Every member package has reached a stable release, and this metapackage now pins them as a verified set.
| Package | Pinned at |
|---|---|
| search-debug | ^1.2.1 |
| search-ranking | ^2.2.0 |
| search-ranking-optimizer | ^1.0.0 |
| search-feedback | ^1.3.0 |
Upgrade note — earlier tags resolve wrongly
Two constraints in the pre-1.0.0 tags were not merely stale but wrong:
^1.3.0for search-ranking excluded its entire 2.x line^0.9.1for search-ranking-optimizer excluded its 1.0.0
A project requiring this bundle at ^0.9.x therefore resolves to a set that no longer reflects the member packages' current releases, or fails to resolve at all. Use ^1.0.0.
What 1.0.0 means here
This package carries no code, so its version tracks compatible combinations, not behavior. 1.0.0 marks the point where every member is itself stable — not a change in what the bundle does.
Unchanged: installation still needs VCS entries
The spryker-community vendor namespace is not yet on Packagist (the name is held by an unrelated GitHub organization). That is a distribution limitation, not a maturity one. Until it is resolved, add a VCS repository entry per package to your own project's composer.json — required for all five packages and for blackbox-optimizer, since Composer reads repositories only from the root project, never from a dependency. See the README for the full snippet.
Full changelog: v0.9.6...v1.0.0