mdka 2.2.3

A HTML to Markdown converter that balances conversion quality with runtime efficiency
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93

name: Create Release

# Triggers on pushing an annotated (or lightweight) release tag, e.g. 2.1.7.
# Verified against this repository's real tag history: matches every clean
# N.N.N release tag (0.1.0 .. 2.1.7) and excludes every pre-release tag
# (1.5.0-rc.1..5, 2.0.0-rc.1..4) and every legacy v-prefixed tag
# (v0.0.6, v0.0.8, v0.0.9, v0.0.10) — see the GitHub Actions filter pattern
# cheat sheet's own semantic-version example ('v[12].[0-9]+.[0-9]+').
on:
  push:
    tags:
      - '[0-9]+.[0-9]+.[0-9]+'

permissions:
  contents: read

defaults:
  run:
    shell: bash

jobs:
  verify-ci:
    runs-on: ubuntu-latest
    timeout-minutes: 30
    permissions:
      actions: read
      contents: read
    steps:
      # Same guard as the four release: created workflows, run here first
      # because this workflow is what creates the release that triggers them.
      - name: Require green CI on the tagged commit
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          GH_REPO: ${{ github.repository }}
        run: |
          set -euo pipefail
          run_id=$(gh run list --commit "${{ github.sha }}" \
                     --workflow ci.yaml --limit 1 --json databaseId \
                     --jq '.[0].databaseId // empty')
          if [ -z "$run_id" ]; then
            echo "::error::No CI run found for ${{ github.sha }}. Refusing to create a release."
            exit 1
          fi
          gh run watch "$run_id" --exit-status

  create-release:
    needs: [verify-ci]
    runs-on: ubuntu-latest
    permissions:
      contents: write
      actions: write

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6

      # Creating the release does NOT start the four sibling workflows.
      # GitHub suppresses release/push/etc. events fired by GITHUB_TOKEN to
      # prevent recursive workflow triggering, so a release created here
      # would otherwise start nothing. workflow_dispatch is the documented
      # exception to that suppression, so the next step dispatches all four
      # explicitly instead of relying on fan-out.
      - name: Create GitHub release
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          tag="${{ github.ref_name }}"
          link="https://github.com/${{ github.repository }}/blob/${tag}/CHANGELOG.md"

          # Point at this version's CHANGELOG section. GitHub's heading anchor
          # includes the release date ("## [2.2.1] - 2026-09-01" -> #221---2026-09-01),
          # so it has to be derived from the heading rather than the version alone.
          # If the heading is not found, the link degrades to the file itself --
          # never to a broken anchor.
          heading=$(grep -m1 "^## \[${tag}\]" CHANGELOG.md || true)
          if [ -n "$heading" ]; then
            anchor=$(printf '%s' "$heading" | sed 's/^## //' | tr -d '[].' | tr ' ' '-' | tr 'A-Z' 'a-z')
            link="${link}#${anchor}"
          fi

          gh release create "${tag}" \
            --title "${tag}" \
            --notes "📖 [Changelog for ${tag}](${link})" \
            --generate-notes

      - name: Start the publishing workflows
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          for wf in release-crates release-npm release-pypi release-executable; do
            echo "Dispatching ${wf}.yaml at ${{ github.ref_name }}"
            gh workflow run "${wf}.yaml" --ref "${{ github.ref_name }}"
          done