Skip to content

EFI: Publishing packages #176

@sheplu

Description

@sheplu

Motivation

By having a simple and unique way to publish package, this would lower the cognitive work needed for captains (and other members) to release and publish a new version of the same package. With a standardized way and GitHub Action, publishing can be done almost automatically.

Expectation

Easy and standardized way to publish the packages or the Express Organization without "specific users" or manual operation

Implementation

Automated way to publish packages (maybe using GitHub Releases)
Build a full automation around it where it is just needed to create a release (or git tag depending on what we want to do)
Limit manual operation
Create a workflow to run all needed tests (quality, performance, security...) before releasing

Status

Part: Organization

Draft

In the past few years, a good number of projects choose to use the organizational scope feature of npm allowing them to publish all packages under a specific scope. By doing so it can help improve the security by limiting attacks based on a package name.
Publishing should also be changed to use the release system of GitHub to simplify contributor life

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions