Merge remote-tracking branch 'origin/main'

.forgejo/workflows/release.yml

@@ -6,10 +6,10 @@ on:
 jobs:
   release:
     if: github.event.issue.title == 'release'
-    runs-on: ubuntu-latest
+    runs-on: docker
     steps:
       - name: Checkout
-        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
+        uses: https://github.com/actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
         with:
           token: ${{ secrets.REPO_MAINTAINER_TOKEN }}
 
@@ -30,7 +30,7 @@ jobs:
           ./tea comment ${{ github.event.issue.number }} "Start creating release"
 
       - name: setup node
-        uses: actions/setup-node@b39b52d1213e96004bfcb1c61a8a6fa8ab84f3e8 # v4.0.1
+        uses: https://github.com/actions/setup-node@b39b52d1213e96004bfcb1c61a8a6fa8ab84f3e8 # v4.0.1
         with:
           node-version: 20
 

.forgejo/workflows/tag.yml

@@ -7,10 +7,10 @@ on:
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: docker
     steps:
       - name: Checkout
-        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
+        uses: https://github.com/actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
 
       - name: setup tea cli
         shell: bash
@@ -21,10 +21,12 @@ jobs:
           mv tea* tea
           chmod +x tea
           ./tea login add --url ${{ github.server_url }} --token ${{ github.token }}
-          
-          ./tea i ls --fields index,title --output simple | grep 'Release ${{ github.ref_name }}' | awk '{print $1}' > release-ticket-id
 
-      - name: comment tag start
+      - name: cache release ticket id
+        shell: bash
+        run: ./tea i ls --fields index,title --output simple | grep 'Release ${{ github.ref_name }}' | awk '{print $1}' > release-ticket-id
+
+      - name: comment & close
         shell: bash
         run: |
           ./tea comment $(cat release-ticket-id) "Start tag"

CHANGELOG.md

@@ -1,3 +1,23 @@
+## [1.6.0](https://git.keine.cloud/oliver/pipeline-test-versioning/compare/v1.5.0...v1.6.0) (2024-02-09)
+
+
+### Bug Fixes
+
+* rename to forgejo ([94b2a6b](https://git.keine.cloud/oliver/pipeline-test-versioning/commit/94b2a6b89b4783ba3ae9b7e8f47896c61a78dfac))
+
+
+### Features
+
+* hostname for "uses" ([f8e85ee](https://git.keine.cloud/oliver/pipeline-test-versioning/commit/f8e85eec3b2d4bf736b05719f263964917476e86))
+* runs on docker ([3aff0f1](https://git.keine.cloud/oliver/pipeline-test-versioning/commit/3aff0f11eb11d652f28895e87d6956578f116306))
+
+## [1.5.0](https://git.keine.cloud/oliver/pipeline-test-versioning/compare/v1.4.13...v1.5.0) (2024-02-01)
+
+
+### Features
+
+* close release ticket from tag ([3a7fdc3](https://git.keine.cloud/oliver/pipeline-test-versioning/commit/3a7fdc345395c3f0d74e8e5eb23543286de41d70))
+
 ## [1.4.13](https://git.keine.cloud/oliver/pipeline-test-versioning/compare/v1.4.12...v1.4.13) (2024-02-01)
 
 

README.md

@@ -1,4 +1,4 @@
-# Gitea action test: Versioning
+# Forgejo action test: Versioning
 
-Is it possible to have automatic versioning like release-please or semantic-release in Gitea?
+Is it possible to have automatic versioning like release-please or semantic-release in Forgejo?
 

version.txt

@@ -1 +1 @@
-1.4.13
+1.6.0