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.

Sign up for GitHub

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

Jump to bottom

Improve support for CI/CD #190

Open
imbrn opened this issue May 16, 2021 · 2 comments · Fixed by #209 or #210
Open

Improve support for CI/CD #190

imbrn opened this issue May 16, 2021 · 2 comments · Fixed by #209 or #210
Labels
Scope: Build Status: Accepted Type: Enhancement
Milestone
v1.5.0

Comments

@imbrn
Copy link
Owner

imbrn commented May 16, 2021

Problem: Nowadays, we have to execute the library deployment process every time we need to produce a new version.

It would be nice to have a complete CI/CD process, where every new merge on the main branch would produce an automatic deployment.

Maybe we should adhere to the semantic-release project for helping us to achieve a commit-based versioning system. 🤔
@sbarfurth
Copy link
Collaborator

Good idea, would target 1.5.0 with this. So once 1.4.0 is released we use the commit format?

@sbarfurth sbarfurth added this to the v1.5.0 milestone May 24, 2021
@sbarfurth sbarfurth self-assigned this May 24, 2021
sbarfurth pushed a commit that referenced this issue May 24, 2021
chore(v8n): add commitizen to enforce angular commit message format
b55b9a3 
ref #190
@sbarfurth sbarfurth mentioned this issue May 24, 2021
Closed
2 tasks
sbarfurth pushed a commit that referenced this issue May 24, 2021
chore: add commitizen to enforce angular commit message format
1917d41 
ref #190
@sbarfurth
Copy link
Collaborator

Merged PRs #209 and #210 were part of this. Only thing missing is automatic versioning now.

This was linked to pull requests Feb 13, 2022
Github Action for publishing releases to NPM #209
Merged
Remove CircleCI in favor of Github Actions #210
Merged
@sbarfurth sbarfurth assigned imbrn and unassigned sbarfurth and imbrn Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Scope: Build Status: Accepted Type: Enhancement
Projects
None yet
Milestone
v1.5.0
2 participants
@imbrn @sbarfurth