With 1.17 releasing soon, we'll get to see if this was the issue very shortly. Worst case scenario the yaml is still messed up, but since the changelog is now the last element, unless it's so badly malformed that the entire action can't run the file should still upload even if the changelog does not.
38 lines
1.1 KiB
YAML
38 lines
1.1 KiB
YAML
name: Release to CurseForge
|
|
|
|
on:
|
|
release:
|
|
types: [ released ]
|
|
|
|
jobs:
|
|
curseforge_release:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout Code
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
- name: Fetch Github Release Asset
|
|
uses: dsaltares/fetch-gh-release-asset@0.0.5
|
|
with:
|
|
token: ${{ secrets.GITHUB_TOKEN }}
|
|
version: ${{ github.event.release.id }}
|
|
file: OpenInv.jar
|
|
|
|
- name: Set CurseForge Variables
|
|
run: . scripts/set_curseforge_env.sh "${{ github.event.release.body }}"
|
|
|
|
- name: Create CurseForge Release
|
|
uses: itsmeow/curseforge-upload@v3
|
|
with:
|
|
token: ${{ secrets.CURSEFORGE_TOKEN }}
|
|
project_id: 31432
|
|
game_endpoint: minecraft
|
|
file_path: ./OpenInv.jar
|
|
display_name: "${{ github.event.release.name }}"
|
|
game_versions: "${{ env.CURSEFORGE_MINECRAFT_VERSIONS }}"
|
|
release_type: release
|
|
changelog_type: markdown
|
|
changelog: "${{ env.CURSEFORGE_CHANGELOG }}"
|