actions/semantic-version
6
0
Fork 0
mirror of https://github.com/PaulHatch/semantic-version.git synced 2025-12-27 04:58:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #163 from jeremybower/update-versions-to-v5.4

Browse source 
Update examples to v5.4.0
This commit is contained in:
Paul Hatcherian 2024-07-19 00:38:58 +02:00 committed by GitHub
commit c4f3793c16
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
contributing.md
View file

@ -20,7 +20,7 @@ There is a debug option which produces diagnostic information. This information
``` ```
- name: Version - name: Version
uses: paulhatch/semantic-version@v5.2.1 uses: paulhatch/semantic-version@v5.4.0
id: version id: version
with: with:
tag_prefix: "" 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 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) - 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. 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.

6
readme.md
View file

@ -73,7 +73,7 @@ it will be given the new version if the build were to be retriggered, for exampl
<!-- start usage --> <!-- start usage -->
```yaml ```yaml
- uses: paulhatch/semantic-version@v5.3.0 - uses: paulhatch/semantic-version@v5.4.0
with: with:
# The prefix to use to identify tags # The prefix to use to identify tags
tag_prefix: "v" tag_prefix: "v"
@ -156,12 +156,12 @@ like `v1.2.3+0-db` could be configured like this:
```yaml ```yaml
- name: Application Version - name: Application Version
id: version id: version
uses: paulhatch/semantic-version@v5.3.0 uses: paulhatch/semantic-version@v5.4.0
with: with:
change_path: "src/service" change_path: "src/service"
- name: Database Version - name: Database Version
id: db-version id: db-version
uses: paulhatch/semantic-version@v5.3.0 uses: paulhatch/semantic-version@v5.4.0
with: with:
major_pattern: "(MAJOR-DB)" major_pattern: "(MAJOR-DB)"
minor_pattern: "(MINOR-DB)" minor_pattern: "(MINOR-DB)"