CI and Release Workflows
Overview
Release preparation starts from the manual Prepare Release workflow in .github/…/prepare-release.yml. It accepts a semantic version, optional previous_version, optional public drawio_ref, dry_run, and override_audit. The job checks out the repo with submodules and full history, uses Node 24, optionally moves the drawio submodule, updates package.json, deletes node_modules and package-lock.json, then runs npm install so the regenerated lockfile has resolved URLs and integrity hashes needed by offline Flatpak/Flathub builds. It generates release-notes.md, records the Electron version from package-lock.json, probes whether jgraph/drawio has a public vX.Y.Z tag before emitting a ChangeLog link, runs npm audit and gates only critical/high runtime dependency vulnerabilities unless override_audit is set, uploads release evidence artifacts for 365 days, and, when not a dry run, pushes releases/vX.Y.Z and opens a PR into dev.
The operator-facing process for that workflow is maintained in doc/RELEASE_PROCESS.md. It documents the intended sequence: ensure drawio-dev's release branch VERSION is the release version, update the public drawio submodule on dev when appropriate, run prepare-release, merge the generated PR, then create and push an annotated v* tag. The tag push is the boundary between preparation and packaging: .github/…/electron-builder.yml and .github/…/electron-builder-win.yml both run only on pushed tags matching v*.
The Linux/macOS packaging workflow is .github/…/electron-builder.yml. It runs a two-OS matrix on ubuntu-latest and macos-latest, checks out this repo with submodules, mints a GitHub App token for jgraph/drawio-dev, checks out the private drawio-dev release branch, validates drawio-dev/VERSION, copies drawio-dev/…/*.min.js and drawio-dev/VERSION into the public drawio submodule tree, removes non-desktop webapp/server material, and preserves viewer-static.min.js for the macOS Quick Look extension. It then installs Node 24, imports the macOS signing certificate into a custom keychain on macOS, runs npm ci, patches the Linux product name to drawio, runs npm run sync, and executes npm run release-linux, which maps to electron-builder --config electron-builder-linux-mac.json --publish always in package.json. The same workflow builds the snap only on Ubuntu via npm run release-snap and uploads it to the edge channel with snapcraft; that snap step is continue-on-error so a snap outage does not fail the release or cancel the macOS job.
The Windows release workflow is .github/…/electron-builder-win.yml. It also checks out drawio-dev with a GitHub App token, copies the private minified editor and VERSION into the public submodule tree, installs Node 24, and runs npm ci. Before building, it downloads a pinned Microsoft.ArtifactSigning.Client NuGet package, extracts Azure.CodeSigning.Dlib.dll, finds a compatible Windows SDK signtool.exe, and exports both paths for the Trusted Signing hook used by the Windows electron-builder configs. It then runs npm run sync and builds Windows arm64 (npm run release-win-arm64), Windows x64 NSIS/MSI (npm run release-win), an unpacked x64 build that is zipped and uploaded to the same GitHub release with gh release upload, and an APPX/MSIX package with auto-update disabled via npm run sync -- disableUpdate and npm run release-appx. The .msix is uploaded as the appx-package workflow artifact, not as a release asset.
The microsoft-store job in .github/…/electron-builder-win.yml depends on the Windows build job. It downloads the appx-package artifact, installs microsoft/microsoft-store-apppublisher@v1.4, configures the Microsoft Store CLI from MS_STORE_TENANT_ID, MS_STORE_SELLER_ID, MS_STORE_CLIENT_ID, and MS_STORE_CLIENT_SECRET, then publishes the .msix to the Store product 9MVVSZK43QQW. .github/…/store-credentials-check.yml is the read-only companion: it is manually dispatched, verifies those four secrets are present, configures the same CLI, and reads the Store listing with msstore apps get 9MVVSZK43QQW so credential rotations can be tested without touching a submission.
Post-publication automation is split into hash and Flathub workflows. .github/…/hash-gen.yml runs on release: published, on a daily cron, and manually. It is serialized by the hash-gen concurrency group, lists recently published non-draft releases, skips any release that already has Files-SHA256-Hashes.txt, takes hashes from GitHub asset digests when available, downloads and hashes assets that lack a sha256: digest, sorts the result, and uploads Files-SHA256-Hashes.txt back to the release. .github/…/flathub-release.yml is intended to open version-bump PRs against flathub/com.jgraph.drawio.desktop, but the workflow file says it has been disabled since 09/2026 because FLATHUB_TOKEN was not configured. When enabled, it runs on release: published, hourly cron, or manual dispatch, compares the target desktop tag to the Flathub manifest, exits if the manifest or an open automation PR already covers it, verifies FLATHUB_TOKEN only when an update is needed, checks out this repo at the release tag and the Flathub packaging repo, regenerates generated-sources.json from the release package-lock.json with flatpak-node-generator, patches the manifest and metainfo, pushes release-vX.Y.Z, opens a Flathub PR, and closes older automation PRs it supersedes.
Personal/fork builds are intentionally separate from official release publishing. .github/…/personal-build.yml is manually dispatched with a platform choice, has only contents: read, sets DRAWIO_UNSIGNED=true and CSC_IDENTITY_AUTO_DISCOVERY=false, checks out submodules without persisting credentials, installs Node 24, installs Linux packaging tools and patches the Linux product name when needed, runs npm ci, runs npm run sync -- disableUpdate, invokes electron-builder with --publish never, and uploads installers from dist/ as workflow artifacts. doc/BUILDING_FOR_PERSONAL_USE.md explains the same contract for fork users: official tag-triggered workflows need private drawio-dev access and signing secrets, while personal builds are unsigned, disable auto-update so the official app does not replace them, and never publish.
Repository issue automation and metadata live under .github/. .github/…/stale.yml runs nightly and uses actions/stale@v10 with issue and pull-request write permissions; after 30 inactive days it labels issues and PRs wontfix and posts the stale message linking to the stale-bot FAQ, then closes them after 3 more days with declined unless they have the notstale label. .github/…/bug_report.md and .github/…/feature_request.md are the active issue templates for this repository and link to the jgraph/drawio-desktop code of conduct; the older .github/bug_report.md and .github/feature_request.md templates point at jgraph/drawio. .github/FUNDING.yml advertises github: jgraph.
Coupling
- If the version source changes, update doc/RELEASE_PROCESS.md, .github/…/prepare-release.yml, .github/…/electron-builder.yml, and .github/…/electron-builder-win.yml together. The prepare workflow writes the requested version into package.json, but the tag build later copies
drawio-dev/VERSIONintodrawio/VERSIONandnpm run syncstamps that internal version into package.json; a mismatch creates or uploads assets to a draft release for the wrong version. - If the public
drawiosubmodule cleanup changes in .github/…/electron-builder.yml, mirror the PowerShell cleanup in .github/…/electron-builder-win.yml. Both workflows stage the privatedrawio-devrelease into the public submodule, remove server/webapp material, and intentionally keepjs/mermaid; diverging cleanup can make platform builds package different editor files. - If Node or dependency-lock behavior changes, update .github/…/prepare-release.yml, .github/…/electron-builder.yml, .github/…/electron-builder-win.yml, .github/…/personal-build.yml, doc/RELEASE_PROCESS.md, and doc/BUILDING_FOR_PERSONAL_USE.md. Prepare-release uses
npm installafter deleting the lockfile so Flatpak has complete resolved URLs and integrity hashes, while release builders usenpm cifrom that committed lockfile. - If Windows signing or Store package formats change, verify .github/…/electron-builder-win.yml, .github/…/store-credentials-check.yml, electron-builder-win.json, electron-builder-win-arm64.json, and electron-builder-appx.json. The release job depends on Trusted Signing environment produced by the workflow, then hands a copied
.msixartifact to the Store job; the credential-check workflow validates the same Store secrets but does not validate package creation. - If release asset names or electron-builder artifact names change, update .github/…/prepare-release.yml, .github/…/electron-builder-win.yml, electron-builder-linux-mac.json, electron-builder-win.json, and electron-builder-win-arm64.json. Release notes link to fixed asset names, the Windows workflow uploads the portable zip by a computed
draw.io-$version-windows.zipname, and hash generation will include whatever assets are present when the release is published. - If Flathub packaging is re-enabled, keep .github/…/flathub-release.yml aligned with .github/…/prepare-release.yml. The Flathub workflow regenerates offline npm/electron sources from the release tag's package-lock.json; prepare-release's from-scratch lockfile generation is what makes that output usable in the Flatpak sandbox.
- If stale labels or issue template requirements change, verify .github/…/stale.yml and .github/…/*.md together. The stale workflow exempts only
notstaleand applieswontfix/declined; template text is the first place maintainers tell reporters what complete issues need to include before automation starts acting on them.
Risks
- .github/…/hash-gen.yml and .github/…/flathub-release.yml both note that
release: publishedevents have been unreliable for this repo since late 2024. If the cron or idempotency guards are removed, published releases may miss Files-SHA256-Hashes.txt or Flathub bump PRs when GitHub drops the release event. - .github/…/flathub-release.yml is disabled because
FLATHUB_TOKENwas not configured. If it is re-enabled without adding a PAT with write access toflathub/com.jgraph.drawio.desktop, the hourly schedule will repeatedly fail once the desktop release is ahead of Flathub. - .github/…/electron-builder.yml deliberately marks the snap build
continue-on-errorand documents snapcraft/LXD/network workarounds. If that flag is removed, snapcraft flakiness can fail an otherwise complete GitHub release and cancel or obscure platform release jobs. - .github/…/electron-builder-win.yml has bug-history comments around the unpacked portable build: a bare
--dirloads no config and previously shipped the portable zip unsigned and without the fuses hook (jgraph/drawio-desktop#2509), and update behavior was adjusted forjgraph/drawio-desktop#2569. If the explicit--config electron-builder-win.json --win --x64 --dir --publish nevercall is simplified, the portable artifact can regress independently of the installer builds. - doc/RELEASE_PROCESS.md warns that re-running failed tag builds reads
drawio-dev'sreleasebranch again. If that branch has moved after the tag was pushed, a re-run can build a different internal editor/version than the reviewed release unless the operator first confirmsdrawio-dev/VERSIONstill matches the tag.