ci: Attempt fix of release workflow
This commit is contained in:
@@ -3,7 +3,7 @@ name: Binary release
|
||||
on:
|
||||
push:
|
||||
tags:
|
||||
- 'v*'
|
||||
- 'v*'
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
@@ -8,7 +8,7 @@ jobs:
|
||||
runs-on: codeberg-tiny
|
||||
steps:
|
||||
- name: Check that the PR is targetting trunk
|
||||
if: ${{ forgejo.base_ref != 'trunk' }}
|
||||
if: ${{ forge.base_ref != 'trunk' }}
|
||||
run: |
|
||||
set -e
|
||||
echo "The PR is not targetting the trunk branch, please fix that."
|
||||
|
||||
@@ -3,7 +3,7 @@ name: Release
|
||||
on:
|
||||
push:
|
||||
tags:
|
||||
- 'v*'
|
||||
- 'v*'
|
||||
|
||||
jobs:
|
||||
build:
|
||||
@@ -49,14 +49,15 @@ jobs:
|
||||
done
|
||||
|
||||
- name: Release
|
||||
uses: https://code.forgejo.org/actions/forgejo-release@v2
|
||||
uses: https://code.forgejo.org/actions/forgejo-release@v2.7.2
|
||||
with:
|
||||
direction: upload
|
||||
hide-archive-link: true
|
||||
release-dir: dist-output
|
||||
release-notes: |
|
||||
Changelog can be found [here](https://codeberg.org/Limine/Limine/src/tag/${{ forgejo.ref_name }}/ChangeLog).
|
||||
Changelog can be found [here](https://codeberg.org/Limine/Limine/src/tag/${{ forge.ref_name }}/ChangeLog).
|
||||
|
||||
Binary release can be found [here](https://codeberg.org/Limine/Limine/src/tag/${{ forgejo.ref_name }}-binary).
|
||||
Binary release can be found [here](https://codeberg.org/Limine/Limine/src/tag/${{ forge.ref_name }}-binary).
|
||||
|
||||
Tarballs are signed using key ID `05D29860D0A0668AAEFB9D691F3C021BECA23821` which can be obtained from a keyserver such as `keyserver.ubuntu.com`.
|
||||
|
||||
|
||||
11
ChangeLog
11
ChangeLog
@@ -1,3 +1,14 @@
|
||||
2025-08-30 Mintsuki <mintsuki@protonmail.com>
|
||||
|
||||
*** Release 9.6.3 ***
|
||||
|
||||
Noteworthy changes compared to the previous release, 9.6.2:
|
||||
|
||||
This is a special hotfix release attempting to address issues with the
|
||||
Forgejo release workflow after the migration to Codeberg.
|
||||
|
||||
Other than that, it has no differences compared to 9.6.2.
|
||||
|
||||
2025-08-30 Mintsuki <mintsuki@protonmail.com>
|
||||
|
||||
*** Release 9.6.2 ***
|
||||
|
||||
@@ -77,9 +77,9 @@ For example, to clone the latest binary release of the `9.x` branch, one can do:
|
||||
```bash
|
||||
git clone https://codeberg.org/Limine/Limine.git --branch=v9.x-binary --depth=1
|
||||
```
|
||||
or, to clone a specific binary point release (for example `9.6.2`):
|
||||
or, to clone a specific binary point release (for example `9.6.3`):
|
||||
```bash
|
||||
git clone https://codeberg.org/Limine/Limine.git --branch=v9.6.2-binary --depth=1
|
||||
git clone https://codeberg.org/Limine/Limine.git --branch=v9.6.3-binary --depth=1
|
||||
```
|
||||
|
||||
In order to rebuild host utilities like `limine`, simply run `make` in the binary
|
||||
|
||||
Reference in New Issue
Block a user