Introducing fully-semantic version searching for packages; via the UI, API, CLI and entitlement tokens.
With semantic versions, Cloudsmith understands the difference between versions, in terms of how a version is represented. For example, we know that 10.2.0 is MAJOR version 10, MINOR version 2 and PATCH version 0 and that 10.2.0 is a higher version than 9.3.1.
Leveraging this, you can now use relational operators, such as > (greater-than), >= (greater-than or equal-to), < (less-than), and <= (less-than or equal-to), when searching for versions. Combined with our boolean search, that means more power than ever before to find the packages you need.
We've also introduced the popular "pessimistic operator", as ~=, which allows you to search for versions that are greater-than or equal-to a specific version, up to versions that are less than the next incompatible level. E.g. version:~=1.2.0 will allow versions between 1.2.0 up to 1.3.0.
This might be most interesting to vendors, who want to sell licenses for a particular version-line of their product and allow customers only access to that range. E.g. For customer purchases a "1.x" edition, that wouldn't give access to "2.x" or beyond. The vendor would use version:~=1.0 as their entitlement restriction.
Tip: If you have any unexpected issues with the semantic version search, you can go back to string-based searching by including globs (*) in your expression, or by using ^ to match the start of the version or $ to match the end of the version. E.g. version:^1.0.0$ will match 1.0.0 exactly, by string-based matching.
We are very pleased to announce that upstream proxying and caching for the Maven package format is now available!
Proxying allows requests for packages not found within your Cloudsmith repository to be directed to another location. Maven Central has been supported as a proxy location for a while now on Cloudsmith - but from today, you can now spec…
In order to streamline things for exciting changes coming up, we've restyled the package detail and package list pages. If you've got a keen eye, you'll also notice that the tags have been restyled too and that there's an extra sneaky edit tags button on the package detail page at the top-right. More details to follow next week!
If you, like many of your contemporaries here, are using Cloudsmith for mission-critical delivery of software, we'll bet you're always interested in better ways to protect your assets.
With today's update, we have added support for restricting the location at which your API key can be used to access your account, programmatically. If an IP doesn't…
The groups for packages will now be by name and package format. So the UI will no longer group together (e.g.) Maven and Docker packages as a single group.
This should make it a little easier to tell what packages you have, based on package format. More improvements for the management of this are planned too. Watch this space!
Apr 27 2020
Keep up to date with our monthly product bulletin
By submitting this form, you agree to our privacy policy