@snyk/error-catalog-nodejs-public 5.21.4 → 5.21.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/src/catalogs/CustomBaseImages-error-catalog.d.ts +3 -3
  3. package/src/catalogs/CustomBaseImages-error-catalog.js +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@snyk/error-catalog-nodejs-public",
3
- "version": "5.21.4",
3
+ "version": "5.21.5",
4
4
  "type": "commonjs",
5
5
  "author": "snyk.io",
6
6
  "license": "Apache-2.0",
package/src/catalogs/CustomBaseImages-error-catalog.d.ts CHANGED
@@ -19,10 +19,10 @@ import { ProblemError } from '../problem-error';
19
19
  * @name VersioningSchemaDoesNotSupportTagError
20
20
  * @description The versioning schema used does not support the given tag. Update the versioning schema to include the tag.
21
21
  *
22
- * Once the tag of the custom base image is correct, the versioning schema must be modified.
23
- * You can use a different versioning schema that supports all tags in the repository or you can update the relevant properties of the versioning schema.
22
+ * Once the tag of the custom base image is correct, the versioning schema must be modified.
23
+ * You can use a different versioning schema that supports all tags in the repository or you can update the relevant properties of the versioning schema.
24
24
  *
25
- * For example, if the repository currently uses Semver, and a new tag "1.2.5.7" needs to be added, then you can use a Custom versioning schema.
25
+ * For example, if the repository currently uses Semver, and a new tag "1.2.5.7" needs to be added, then you can use a Custom versioning schema.
26
26
  *
27
27
  * See more:
28
28
  * - [https://docs.snyk.io/scan-using-snyk/snyk-container/use-snyk-container-from-the-web-ui/use-custom-base-image-recommendations/versioning-schema-for-custom-base-images](https://docs.snyk.io/scan-using-snyk/snyk-container/use-snyk-container-from-the-web-ui/use-custom-base-image-recommendations/versioning-schema-for-custom-base-images)
package/src/catalogs/CustomBaseImages-error-catalog.js CHANGED
@@ -23,10 +23,10 @@ const problem_error_1 = require("../problem-error");
23
23
  * @name VersioningSchemaDoesNotSupportTagError
24
24
  * @description The versioning schema used does not support the given tag. Update the versioning schema to include the tag.
25
25
  *
26
- * Once the tag of the custom base image is correct, the versioning schema must be modified.
27
- * You can use a different versioning schema that supports all tags in the repository or you can update the relevant properties of the versioning schema.
26
+ * Once the tag of the custom base image is correct, the versioning schema must be modified.
27
+ * You can use a different versioning schema that supports all tags in the repository or you can update the relevant properties of the versioning schema.
28
28
  *
29
- * For example, if the repository currently uses Semver, and a new tag "1.2.5.7" needs to be added, then you can use a Custom versioning schema.
29
+ * For example, if the repository currently uses Semver, and a new tag "1.2.5.7" needs to be added, then you can use a Custom versioning schema.
30
30
  *
31
31
  * See more:
32
32
  * - [https://docs.snyk.io/scan-using-snyk/snyk-container/use-snyk-container-from-the-web-ui/use-custom-base-image-recommendations/versioning-schema-for-custom-base-images](https://docs.snyk.io/scan-using-snyk/snyk-container/use-snyk-container-from-the-web-ui/use-custom-base-image-recommendations/versioning-schema-for-custom-base-images)