Skip to content

fix: restore report-generation pipeline on main (Chromium sandbox flag) - #74

Merged
jhosepmyr merged 2 commits into
mainfrom
develop
Jul 10, 2026
Merged

fix: restore report-generation pipeline on main (Chromium sandbox flag)#74
jhosepmyr merged 2 commits into
mainfrom
develop

Conversation

@jhosepmyr

Copy link
Copy Markdown
Contributor

Description of Change

Section modified: Release merge — developmain, restoring .github/workflows/generate-pdf.yml

Motivation: The push of PR #72 (developmain) broke the Generate PDF from README workflow on main: the new "Render full HTML for Word conversion" step launches Chromium via md-to-pdf --as-html without the --no-sandbox --disable-setuid-sandbox flags, which GitHub Actions runners require. PR #73 fixed this on develop; this PR ships that fix to main so the pipeline runs green again on the next push.

Included:


Type of Change

  • New section or subsection
  • Update to existing content
  • New diagram or image
  • Typo or writing correction
  • Incorrect data or information fix
  • Structure reorganization (no content change)
  • Asset change (image replacement)

Checklist Before Requesting Review

  • The PR targets develop (not main) — N/A, this PR is developmain by design (hotfix release)
  • The branch name follows the convention feature/* or bugfix/* — N/A, source branch is develop
  • Commits follow the Conventional Commits convention (feat:, fix:, docs:, etc.)
  • CHANGELOG.md has been updated with the change made
  • New images are placed in the correct assets/ subfolder — N/A
  • Image links in the README render correctly — N/A
  • Spelling of added or modified content has been reviewed — N/A
  • No generated files are included (.pdf, .docx, .html)

Screenshots or Evidence (optional)

Failing run on main: workflow Generate PDF from README, run 29069830937 (Chromium FATAL: No usable sandbox!). Fix verified locally and merged to develop via #73.


Suggested Reviewers

@jhosepmyr

jhosepmyr added 2 commits July 9, 2026 23:49
md-to-pdf --as-html still launches Puppeteer/Chromium under the hood, but
this step was missing the --no-sandbox/--disable-setuid-sandbox launch
options already used by the PDF step. On GitHub Actions runners (no
usable user namespace sandbox), Chromium crashed with 'No usable sandbox',
breaking the CI run on push to main.
…x-flag

fix: pass Chromium sandbox flags to the HTML render step
@jhosepmyr
jhosepmyr merged commit fafbb96 into main Jul 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant