fix(curseforge): upload changelog as HTML so release notes aren't escaped

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code

[tastybento]

Problem

CurseForge shows our release notes with every markdown character backslash-escaped — headings, bullets, inline code and links all render as their literal source (\# What's new, \* \*\*Miner minions…\*\*, \`NullPointerException\`, my\_island\_\*, \[#525\]). Example: the AOneBlock 1.25.1 release.

Root cause

CurseForge's upload API defaults changelogType to text, and in practice its markdown mode escapes the content for literal display. Nothing in this workflow adds the escaping — the changelog.md artifact and the jq-built JSON are both clean markdown; CurseForge does the escaping on its side when given changelogType: markdown.

Fix

• Render the markdown changelog to HTML via GitHub's /markdown API (gh api --method POST /markdown, using the already-present github.token) and upload it with changelogType: html, which CurseForge renders correctly. Falls back to raw markdown if the render call fails, so a publish is never blocked by it.
• Strip CRLF carriage returns from the changelog in the shared prep step so every platform (CurseForge, Hangar) gets clean LF text.

Only the CurseForge path changes behaviour; Hangar/Modrinth are markdown-native and unaffected (they just benefit from the CR strip).

Testing

Verified the gh /markdown conversion locally against the actual AOneBlock 1.25.1 release body — it produces correct HTML (<h1>, <strong>, <code>, <a href>, <ul>) and the resulting metadata JSON round-trips cleanly. YAML validated.

After merge, addon publish.yml files that pin this reusable workflow to a SHA (e.g. AOneBlock at fe4b1f0) need their pin bumped to pick up the fix.

🤖 Generated with Claude Code