Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package publish automation #27

Open
raulfdm opened this issue Jun 25, 2020 · 0 comments
Open

Package publish automation #27

raulfdm opened this issue Jun 25, 2020 · 0 comments
Assignees
Labels

Comments

@raulfdm
Copy link
Collaborator

raulfdm commented Jun 25, 2020

Hi everyone.

Since I was add as collaborator, I'd propose some changes to improve this library quality.
In a couple days I'll create more proposals and pull requests but this one is about automating the deployment process.

Proposal

My idea here is to use semantic-release to do this process for us.

For those who doesn't know what's this about, semantic release takes care of our versioning using Angular commit message versioning:
image

It means each commit made needs to follow this structure because it'll be used to:

  1. decide what version would be next. If a commit with fix prefix is merged into master, then semantic release will automatically bump from 2.2.1 to 2.2.2 (minor version) for example;
  2. Auto generates Change log when it happens;
  3. Auto generates tag publish;

Needs

To set this flow only the only thing I need is a NPM_TOKEN environment variable to publish to npm and a GH_TOKEN to publish change logs and tags:

image

The rest is on me :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants