![]() ![]() ![]() You can see an example of how the changelog would look like in the Artifact Hub UI here. Artifact Hub can generate and display a ChangeLog based on the entries in the changes field in all your chart versions. This annotation is used to provide some details about the changes introduced by a given chart version. artifacthub.io/changes (yaml string, see example below).In the case that the prediction isn’t correct but your package doesn’t fit well in any of the categories supported, you can use the special value skip-prediction in the category field to prevent an incorrect classification. If you notice that the prediction isn’t correct, we really appreciate that you submit the correct category as it helps us to train and improve the model. When a category is not provided, Artifact Hub will try to predict one from the package’s keywords by using a machine learning-based model. Please use only one category from the following list: ai-machine-learning, database, integration-delivery, monitoring-logging, networking, security, storage or streaming-messaging. This annotation allows publishers to provide the package’s category. artifacthub.io/category (string, see example below).Please note that the alternative name must be a substring of the name, or the name must be a substring of the alternative name. So in cases like the previous examples, it can help ranking them higher in the search results. This situation can be improved by providing an alternative name for your package, which will be given the same weight as the package name when indexing. When searching for packages, Artifact Hub gives preference to exact matches in names, so sometimes the top results may not be what users would expect. Users often may type any of the options and expect the same results. Some examples would be postgres / postgresql or mongodb / mongo. ![]() Sometimes a package can be identified by two similar names. ![]()
0 Comments
Leave a Reply. |