chore: update version format to include 'v' prefix and adjust related configurations
This commit is contained in:
@@ -1,5 +1,5 @@
|
|||||||
[bumpversion]
|
[bumpversion]
|
||||||
current_version = 0.1.9
|
current_version = v0.1.9
|
||||||
commit = True
|
commit = True
|
||||||
tag = True
|
tag = True
|
||||||
|
|
||||||
|
|||||||
4
.github/workflows/manual-build.yml
vendored
4
.github/workflows/manual-build.yml
vendored
@@ -69,12 +69,12 @@ jobs:
|
|||||||
tags: |
|
tags: |
|
||||||
ghcr.io/${{ github.repository }}:${{ env.COMMIT_SHA }}
|
ghcr.io/${{ github.repository }}:${{ env.COMMIT_SHA }}
|
||||||
ghcr.io/${{ github.repository }}:${{ env.BRANCH_NAME }}
|
ghcr.io/${{ github.repository }}:${{ env.BRANCH_NAME }}
|
||||||
ghcr.io/${{ github.repository }}:${{ env.BRANCH_NAME }}-${{ env.VERSION }}
|
ghcr.io/${{ github.repository }}:${{ env.VERSION }}-${{ env.BRANCH_NAME}}
|
||||||
- name: Create GitHub Release
|
- name: Create GitHub Release
|
||||||
uses: softprops/action-gh-release@v2
|
uses: softprops/action-gh-release@v2
|
||||||
with:
|
with:
|
||||||
tag_name: |
|
tag_name: |
|
||||||
${{ env.BRANCH_NAME }}-${{ env.VERSION }}
|
${{ env.VERSION }}-${{ env.BRANCH_NAME }}
|
||||||
name: |
|
name: |
|
||||||
${{ env.BRANCH_NAME }} Release ${{ env.VERSION }}
|
${{ env.BRANCH_NAME }} Release ${{ env.VERSION }}
|
||||||
body: |
|
body: |
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
__version__ = "0.1.9"
|
__version__ = "v0.1.9"
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Whats up in Jellyplist 0.1.9?
|
# Whats up in Jellyplist v0.1.9?
|
||||||
## ⚠️ BREAKING CHANGE: docker-compose.yml
|
## ⚠️ BREAKING CHANGE: docker-compose.yml
|
||||||
>![WARNING]
|
>[!WARNING]
|
||||||
>In this release I´ve done some rework so now the setup is a bit easier, because you don´t have to spin up the -worker -beat container, these are now all in the default container and managed via supervisor. This means you have to update your `docker-compose.yml` when updating!
|
>In this release I´ve done some rework so now the setup is a bit easier, because you don´t have to spin up the -worker -beat container, these are now all in the default container and managed via supervisor. This means you have to update your `docker-compose.yml` when updating!
|
||||||
|
|
||||||
So now your compose file should look more or less like this
|
So now your compose file should look more or less like this
|
||||||
@@ -1 +1 @@
|
|||||||
__version__ = "0.1.9"
|
__version__ = "v0.1.9"
|
||||||
|
|||||||
Reference in New Issue
Block a user