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

ci: automated release process #890

Closed
5 tasks
fryorcraken opened this issue Aug 17, 2022 · 1 comment · Fixed by #1155
Closed
5 tasks

ci: automated release process #890

fryorcraken opened this issue Aug 17, 2022 · 1 comment · Fixed by #1155
Assignees

Comments

@fryorcraken
Copy link
Collaborator

fryorcraken commented Aug 17, 2022

This is a change request

Problem

The release process is manual, hence it is difficult to release early, release often.

This repo will become a multi-repo soon #802 and hence we need to make the releasing of the various packages easier.

Ideally, one button click should be enough for a maintainer to release and publish.

Also, automation of the changelog should be considered, using Conventional Commits

Acceptance Criteria

  • Changelog is maintained from commits using conventional commits
  • New PR automatically opens when changes are merged, version (patch, minor) is deduced from conventional commits (breaking change or not)
  • Maintainer can merge PR for release to happen
  • Minimum manual action should still be needed from the maintainer
  • Automated release and publication of all merged PR under a release candidate version (ie 0.23.0-<short commit hash>) with a next tag on npmjs.com Auto-release merged PRs #896

Notes

Check out the following repos for ideas:

@weboko
Copy link
Collaborator

weboko commented Feb 8, 2023

How it will work with release-please:

  • PR will be automatically created and updated based on master;
  • major increment will be made only if breaking change is introduced as per conventional commit spec;
  • the only action is for maintainer to complete a PR;

@weboko weboko moved this from In Progress to Code Review / QA in Waku Feb 8, 2023
@github-project-automation github-project-automation bot moved this from Code Review / QA to Done in Waku Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants