Generated from fhir-harness/processes/content/ig-release.bpmn by gen-processes-viz.ts — do not edit here. All processes · fhir-harness processes

An IG release: the owner tags, a draft is built, the owner publishes

Process_IgRelease · advisory · 5 step(s)

How an IG repository’s release is cut, and how a missed one is caught up (skill ig-binary-artefacts §”Releasing”). (Owner, 2026-11-10: “need to add this to process (and how to catchup if not tagged) of build”.)

THE RULE. A release is a governance decision. The owner tags the IG’s CURRENT version from sushi-config.yaml, v<version>, on the default branch. The tag starts the IG’s ig-release.yml caller, which builds the tag in full and makes a GitHub DRAFT release carrying package.tgz (and its R4/R4B variants), ast-data.zip and SHA256SUMS. The owner publishes the draft. An agent never chooses a version, never pushes a tag and never publishes a release.

THE CATCH-UP. Every AST refresh of the default branch runs ig-release.ts check (advisory, never failing the run): an untagged current version is reported with the commit that set it, for the owner to tag; a tag with no release is reported with the by-hand run of the release workflow; a draft is reported as waiting for the owner.

The site is not the release: it is published from the AST cache (ig-ast-cache.bpmn) and carries none of these files.

BPMN diagram: An IG release: the owner tags, a draft is built, the owner publishes

How it connects

  • Called by: no call activity names this process
  • Calls: none
  • Presented on: no docs page section shows this diagram
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
Release check (advisory)build-pipelineThe Is the current version tagged and released? (advisory) step of fhir-harness’s ig-ast-refresh.yml. Reads sushi-config.yaml, the tags and the release list; writes nothing.
Owner (release authority, a person)publication-managerHolds release-authorization: decides that a version is released by tagging it, and publishes the draft. Never an agent: an agent reports what is missing and stops.
IG release (GitHub runner: full build, draft release)ig-publisher-servicefhir-harness’s reusable .github/workflows/ig-release.yml, run in the IG repository through its caller (templates/ig-repo-site/ig-release.yml).

Steps

Every one of the 5 step(s) is documented.

steplaneskill / sub-processwhat it does
Tag the IG’s current version
Task_Tag
Owner (release authority, a person)ig-binary-artefacts
ig-publication
The owner tags the commit that set the version with v<version> (for example v0.2.0) and pushes the tag. A releaseLabel of ci-build, ballot or draft, or a version with a suffix, makes it a pre-release (ig-release.ts kind). ig-release.ts check names the commit: the newest one whose diff of sushi-config.yaml sets that version, else HEAD.
Build the tag in full and make the draft release
Task_ReleaseBuild
IG release (GitHub runner: full build, draft release)ig-binary-artefactsig-release.yml (Tool ig-release): ig-ast-refresh.yml with force and release (never incremental), then ig-release.ts assets gathers package.tgz (and package.r4.tgz, package.r4b.tgz), ast-data.zip (the AST, Libraries with their ELM) and SHA256SUMS, and ig-release.ts draft makes or refreshes the GitHub draft for the tag. A tag with a published release is refused.
Publish the draft release
Task_Publish
Owner (release authority, a person)ig-binary-artefactsThe owner reads the draft’s files and publishes it on GitHub: Task_AuthorizeRelease of draft-to-publication.bpmn. Until then only the repository’s writers see it and releases.json leaves it out.
Check the current version’s tag and release
Task_Check
Release check (advisory)ig-binary-artefactsbun run fhir-harness/scripts/ig-release.ts check --ig . --repo <owner/repo> (Tool ig-release). Prints one notice per finding: version X is untagged: the owner tags commit <sha> with vX, or tag vX has no release: run "IG release (draft)" (ig-release.yml) by hand with tag vX, or that a draft waits for the owner. Exits 0 always; never tags and never releases.
Run IG release (draft) by hand for the tag
Task_RunRelease
Owner (release authority, a person)ig-binary-artefactsActions → “IG release (draft)” → Run workflow, input tag = v<version>. For a tag pushed before the IG carried the caller, or whose run failed.

Decisions

Every one of the 2 decision(s) is documented.

decisionwhat decides itbranches
Version tagged?
GW_Tagged
Answered by the check: v<version> exists locally or on origin.no → Tag the IG’s current version
yes → Tag released?
Tag released?
GW_Released
Answered by the check from the repository’s release list (a draft is visible only to a token that may write the repository).no release → Run IG release (draft) by hand for the tag
a draft → Publish the draft release
published → Released

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev