Skip to content

Automatically publish beta releases to make manual testing easier #637

@garethbowen

Description

@garethbowen

Description

Publish unreleased features in beta packages to make it easy to test and iterate on the feature before merging to main.

Currently it is difficult to integrate web forms code in Central, including requiring dev environments of both central and web forms which is then difficult to deploy where QA, designers, and user advocates can access it. This adds friction to the feedback loop which slows the process down significantly, and is error prone.

Instead we should automatically publish the build artifact in a way that is easy to integrate with Central or deploy on its own for testing.

Depending on the outcome of #535 this could either be an npm package or a docker image using something like GitHub Packages so it doesn't end up mistakenly being used in production. The version of the artifact could be based on the name of the branch which means you always get the latest version of that feature.

User Stories

  • As a QA,
    I want to be able to deploy web-forms features before shipping,
    so that I can test them thoroughly.

Dependencies

This should be done after

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions