quarto-publish: make output-dir the single source of truth (forward it to `quarto render`)

[d-morrison]

Already resolved on main — closing.

quarto-publish/action.yml no longer renders via quarto-dev/quarto-actions/render@v2. The "Render Quarto project" step is now a run: shell step that forwards the input to the CLI:

    - name: Render Quarto project
      shell: bash
      env:
        PROJECT_PATH: ${{ inputs.path }}
        OUTPUT_DIR: ${{ inputs.output-dir }}
      run: |
        set -euo pipefail
        quarto render "$PROJECT_PATH" --output-dir "$OUTPUT_DIR"

and the output-dir input doc now reads "Forwarded to quarto render --output-dir, so this input is authoritative — it overrides any output-dir set in the project's _quarto.yml." So the input is the single source of truth, exactly as proposed here.

This landed in PR #55 ("quarto-publish: forward output-dir to render…", commit 7722b8e) before this follow-up issue was filed. Nothing left to do.

[d-morrison]

Already resolved on main by #55 (commit 7722b8e), which landed the same fix the closed PR #42 had attempted.

quarto-publish/action.yml now renders via a run: step that forwards the input to the CLI:

quarto render "$PROJECT_PATH" --output-dir "$OUTPUT_DIR"

and the output-dir input docs now state it is authoritative (overrides _quarto.yml). The selftest's publish job proves it: the fixture's _quarto.yml declares output-dir: _from_quarto_yml while the composite is given output-dir: docs, so a green build confirms the input wins.

Closing as completed.

---

Generated by Claude Code