Merge remote-tracking branch 'origin/master'

CHANGELOG.md

@@ -8,12 +8,12 @@ All notable changes to this package will be documented in this file.
 
 ## v0.3.0
 
-* upgrade `wnx/php-swiss-cantons` to v3.0
+- upgrade `wnx/php-swiss-cantons` to v3.0
 
 ## v0.2.0
 
-* upgrade `wnx/php-swiss-cantons` to v2.1
+- upgrade `wnx/php-swiss-cantons` to v2.1
 
 ## v0.1.0
 
-* initial release
+- initial release

CONTRIBUTING.md

@@ -1,5 +1,5 @@
 ## Coding Guidelines
 
-* This package follows the [coding guidelines](https://github.com/laravel/framework/blob/master/CONTRIBUTING.md#coding-guidelines) used by Laravel.
-* Pull requests for the latest major release MUST be sent to the master branch.
-* To preserve the quality of the package, only **tested** code changes will by reviewed.
+- This package follows the [coding guidelines](https://github.com/laravel/framework/blob/master/CONTRIBUTING.md#coding-guidelines) used by Laravel.
+- Pull requests for the latest major release MUST be sent to the master branch.
+- To preserve the quality of the package, only **tested** code changes will by reviewed.

README.md

@@ -8,7 +8,6 @@
 [![StyleCI](https://styleci.io/repos/241097556/shield)](https://styleci.io/repos/241097556)
 [![Total Downloads](https://img.shields.io/packagist/dt/elbgoods/laravel-swiss-canton-rule.svg?style=flat-square)](https://packagist.org/packages/elbgoods/laravel-swiss-canton-rule)
 
-
 This package provides multiple validation rules to validate swiss cantons.
 It's based on [wnx/php-swiss-cantons](https://github.com/stefanzweifel/php-swiss-cantons).
 

SECURITY.md

@@ -5,15 +5,16 @@
 This package has no LTS releases - this means that we will only support the latest minor release with feature updates.
 We have never had any security vulnerabilities and therefore we don't promise any list of versions.
 Instead we will determine this on a case by case basis - depending on factors like:
-* vulnerable versions
-* age of the versions
-* usage of the versions (packagist downloads)
-* effort needed to fix it in the versions
+
+- vulnerable versions
+- age of the versions
+- usage of the versions (packagist downloads)
+- effort needed to fix it in the versions
 
 We will do our best to fix security issues as and when they become apparent. We will attempt inform all users about possible issues.
 
 ## Reporting a Vulnerability
 
 Due to the fact that security vulnerabilities could harm users, we ask that you don't use the public issue tracker to report them.
 Please write a mail to [moin@elbgoods.de](mailto:moin@elbgoods.de).
-We will either create a public issue/security alert, or we will fix the vulnerability and inform users afterwards. 
+We will either create a public issue/security alert, or we will fix the vulnerability and inform users afterwards.