diff --git a/contributing.md b/contributing.md index 7e8fe0f..fe5da64 100644 --- a/contributing.md +++ b/contributing.md @@ -20,7 +20,7 @@ There is a debug option which produces diagnostic information. This information ``` - name: Version - uses: paulhatch/semantic-version@v5.2.1 + uses: paulhatch/semantic-version@v5.4.0 id: version with: tag_prefix: "" @@ -102,4 +102,4 @@ Additionally a few formatter provide modular behavior to these step: - A version formatter is used to format output version string - A user formatter is used to format the user information in the output (JSON and CSV are provided in the default implementation) -Each one includes at least one default, but can be replaced by a custom provider by implementing the appropriate interface and updating the `ConfigurationProvider` to return your action instead. This should allow you to continue to merge in changes from the main project as needed with minimal conflict. \ No newline at end of file +Each one includes at least one default, but can be replaced by a custom provider by implementing the appropriate interface and updating the `ConfigurationProvider` to return your action instead. This should allow you to continue to merge in changes from the main project as needed with minimal conflict. diff --git a/readme.md b/readme.md index 86cfc75..7393064 100644 --- a/readme.md +++ b/readme.md @@ -73,7 +73,7 @@ it will be given the new version if the build were to be retriggered, for exampl ```yaml -- uses: paulhatch/semantic-version@v5.3.0 +- uses: paulhatch/semantic-version@v5.4.0 with: # The prefix to use to identify tags tag_prefix: "v" @@ -156,12 +156,12 @@ like `v1.2.3+0-db` could be configured like this: ```yaml - name: Application Version id: version - uses: paulhatch/semantic-version@v5.3.0 + uses: paulhatch/semantic-version@v5.4.0 with: change_path: "src/service" - name: Database Version id: db-version - uses: paulhatch/semantic-version@v5.3.0 + uses: paulhatch/semantic-version@v5.4.0 with: major_pattern: "(MAJOR-DB)" minor_pattern: "(MINOR-DB)"