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

Setup CI for deployment of packages #120

Closed
2 of 5 tasks
vahiwe opened this issue Nov 13, 2021 · 1 comment · Fixed by #197
Closed
2 of 5 tasks

Setup CI for deployment of packages #120

vahiwe opened this issue Nov 13, 2021 · 1 comment · Fixed by #197
Assignees
Labels
Epic p0 Adress asap.

Comments

@vahiwe
Copy link

vahiwe commented Nov 13, 2021

Overview

This project needs a CI that automates the deployment of the packages based on commit messages. Any new change to a specific package should trigger the bump and publish.

Tasks

@bestatigen
Copy link
Collaborator

bestatigen commented Nov 14, 2021

This project needs a CI that automates the deployment of the packages.

Yes, based on commit messages (see Semantic Release), but being this a monorepo I found Semantic Release Monorepo). Open to different workflows if you have any other proposals.

Any new commit with a change to package.json will publish the packages.

It's actually "any new change to a specific package" that should trigger the bump and publish.

The release functionality on GitHub could also be used to trigger the deployment.

At the moment builds are automatically deployed to Vercel, either on master or on a pull request for testing.

An automation token needs to be generated for authentication purposes.

You probably only need an NPM token for this; We can see if there is anything else necessary and set it up.


The goal is also to make good use of new yarn functionalities, like the release flow, and for that, We should try to upgrade to the latest yarn and make sure it doesn't break anything of what we have already, as it introduces a few major changes.

Thanks! 🙂

@bestatigen bestatigen linked a pull request Nov 14, 2021 that will close this issue
@bestatigen bestatigen moved this to Sprint Backlog in Sprints Nov 15, 2021
@bestatigen bestatigen moved this from Sprint Backlog to Product Backlog in Sprints Nov 29, 2021
@sekaiking sekaiking self-assigned this Dec 18, 2021
@sekaiking sekaiking moved this from Product Backlog to In Progress in Sprints Dec 24, 2021
@sekaiking sekaiking linked a pull request Dec 25, 2021 that will close this issue
8 tasks
@sekaiking sekaiking moved this from In Progress to Review/QA in Sprints Jan 3, 2022
Repository owner moved this from Review/QA to Done in Sprints Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic p0 Adress asap.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants