Skip to content

Correct Build Installers artifact-upload documentation #13

Closed

Description

@eimexdev

Part of OpenBeat v0.1.0 public launch map.

Question

What documentation changes make the Build Installers artifact-upload behavior match the workflow exactly?

Problem

docs/development.md says push and pull-request builds upload installer artifacts. The workflow now builds on those events but uploads artifacts only for workflow_dispatch and workflow_call.

Work

  • Update the development and release documentation to match the workflow.
  • Explain when a contributor should use a manual build versus the Release workflow.
  • Confirm the release checklist tells maintainers where the downloadable artifacts come from.

Acceptance criteria

The documented artifact behavior exactly matches .github/workflows/build-installers.yml.

Activity

  1. added this to the v0.1.0 public launch milestone on Jul 16, 2026
  2. added
    documentationImprovements or additions to documentation
    launchRequired for the public launch
    releaseRelease engineering and publishing
    on Jul 16, 2026
  3. self-assigned this
    on Jul 25, 2026
  4. eimexdev commented on Jul 25, 2026

    @eimexdev
    OwnerAuthor

    Resolved by Correct Build Installers artifact-upload documentation.

    The documentation now matches the workflows: push and pull-request runs build without uploading; manually dispatched Build Installers runs upload seven-day test artifacts; and the Release workflow builds and attaches the durable distribution assets to a draft GitHub Release. The release checklist now directs maintainers to smoke-test those exact draft Release assets before publishing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationlaunchRequired for the public launchreleaseRelease engineering and publishingwayfinder:taskConcrete task on a Wayfinder route

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions