As organizations use Cloudsmith to manage increasingly large volumes of packages and metadata, the demands on search have changed. To ensure we provide a performant and reliable search experience for all customers, we’ve moved from an implicit to an explicit search model.
By default, if you just enter a search phrase without any additional parameters, searches now match package name only. To search on other fields, such as version, format, or metadata, you’ll need to specify those fields explicitly.
You can find a full list of supported fields and query examples in our search syntax documentation.
Key Highlights
- Faster Searches: Search is more performant, especially for customers with large workspaces that contain lots of artifact data. (If you’ve encountered 504 timeouts before, this change should eliminate them.)
- Stronger Entitlement Token Security: Token download restrictions now default to package name matching only, minimizing unintended matches and strengthening access control.
What You Should Do
- Review and Update Your Queries: If you rely on entitlement tokens or search using terms beyond package names, you’ll need to ensure your queries are updated to include specific search terms and that your tokens are scoped appropriately under the new defaults. We’ve reviewed most customer configurations and expect minimal impact, but it’s worth confirming. If you have any questions or need help updating your queries, contact us - we’re here to help!
