Skip to content

Create a dev release flow #26

Open
Open

Description

@mcollina
No description provided.

Activity

  1. Qard commented on May 31, 2025

    @Qard
    Member

    I think this will require using main as the dev release branch and then having separate release line branches so we can apply the branch protection to each of them and have the npm publish token accessible securely. So we would need to land (and possibly revert or follow-up) changes for it to get a dev release. I'm not sure if we can deploy directly from PR branches securely. 🤔

  2. mcollina commented on May 31, 2025

    @mcollina
    MemberAuthor

    We do this in platformatic/platformatic by whitelisting specific branch manually when needed. Or we could apply it with a wildcard "prerelease/*"

  3. added theissue type on Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions