docs: change release reference in rules documentation

zavoloklom · Dec 15, 2024 · 39f6745 · 39f6745
1 parent fe4f67f
commit 39f6745
Show file tree

Hide file tree

Showing 18 changed files with 23 additions and 23 deletions.
diff --git a/docs/errors/invalid-schema.md b/docs/errors/invalid-schema.md
@@ -29,7 +29,7 @@ To keep the schema current, you can manually update it and contribute to the pro
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/errors/invalid-yaml.md b/docs/errors/invalid-yaml.md
@@ -33,7 +33,7 @@ the YAML structure, those issues will not be flagged by this rule either.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/__TEMPLATE__.md b/docs/rules/__TEMPLATE__.md
@@ -32,7 +32,7 @@ Long rule description, why you should use it
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-build-and-image-rule.md b/docs/rules/no-build-and-image-rule.md
@@ -67,7 +67,7 @@ process. Therefore, this rule enforces that each service should only use one of
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-duplicate-container-names-rule.md b/docs/rules/no-duplicate-container-names-rule.md
@@ -49,7 +49,7 @@ which can disrupt the container management process and network connections.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-duplicate-exported-ports-rule.md b/docs/rules/no-duplicate-exported-ports-rule.md
@@ -78,7 +78,7 @@ ensure that environment variables used for ports are unique or manually check fo
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-quotes-in-volumes-rule.md b/docs/rules/no-quotes-in-volumes-rule.md
@@ -42,7 +42,7 @@ enforcing this rule, we ensure a more reliable and consistent configuration.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-unbound-port-interfaces-rule.md b/docs/rules/no-unbound-port-interfaces-rule.md
@@ -3,11 +3,11 @@
 When specifying ports for services in Docker Compose, it is recommended to explicitly set the host interface or IP
 address to prevent accidental exposure to the network.
 
-- **Rule Name**: no-unbound-port-interfaces
-- **Type**: error
-- **Category**: security
-- **Severity**: major
-- **Fixable**: no
+- **Rule Name:** no-unbound-port-interfaces
+- **Type:** error
+- **Category:** security
+- **Severity:** major
+- **Fixable:** false
 
 ## Problematic Code Example
 
@@ -85,7 +85,7 @@ skip IP interface checks in such cases.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [2.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v2.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/no-version-field-rule.md b/docs/rules/no-version-field-rule.md
@@ -44,7 +44,7 @@ longer requires the "version" field. If you are working with older versions of D
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/require-project-name-field-rule.md b/docs/rules/require-project-name-field-rule.md
@@ -37,7 +37,7 @@ accidental conflicts and improve the organization of your Docker environment.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/require-quotes-in-ports-rule.md b/docs/rules/require-quotes-in-ports-rule.md
@@ -94,7 +94,7 @@ If you want to enforce the use of double quotes around port mappings you can do
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 Handling `expose` section is added in [2.0.0](https://github.com/zavoloklom/docker-compose-linter/releases)
 

diff --git a/docs/rules/service-container-name-regex-rule.md b/docs/rules/service-container-name-regex-rule.md
@@ -39,7 +39,7 @@ names are properly formatted according to Docker's naming conventions.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/service-dependencies-alphabetical-order-rule.md b/docs/rules/service-dependencies-alphabetical-order-rule.md
@@ -66,7 +66,7 @@ large configurations.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/service-image-require-explicit-tag-rule.md b/docs/rules/service-image-require-explicit-tag-rule.md
@@ -86,7 +86,7 @@ If you provide a `prohibitedTags` option, only the tags listed in the `prohibite
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/service-keys-order-rule.md b/docs/rules/service-keys-order-rule.md
@@ -251,7 +251,7 @@ If certain groups are not specified in the `groups` option, the default key orde
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/service-ports-alphabetical-order-rule.md b/docs/rules/service-ports-alphabetical-order-rule.md
@@ -57,7 +57,7 @@ configurations.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/services-alphabetical-order-rule.md b/docs/rules/services-alphabetical-order-rule.md
@@ -48,7 +48,7 @@ locate and manage services within the configuration file.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References
 

diff --git a/docs/rules/top-level-properties-order-rule.md b/docs/rules/top-level-properties-order-rule.md
@@ -108,7 +108,7 @@ grouped together and sorted alphabetically.
 
 ## Version
 
-This rule was introduced in Docker-Compose-Linter [1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
+This rule was introduced in [v1.0.0](https://github.com/zavoloklom/docker-compose-linter/releases).
 
 ## References