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

[WIP] Feat semantic release #80

wants to merge 29 commits into from


None yet
1 participant
Copy link

PaulRBerg commented Mar 29, 2019


Versioning is hard. Humans make a lot of mistakes.


Use multi-semantic-release (based on the core semantic-release) to automate versioning.

Packages Updated

All of them. Also created a new one called monorepo-scripts.


  • Prefix PR title with [WIP] if necessary.
  • Write tests for added code when needed.
  • Update documentation when needed.

PaulRBerg added some commits Mar 26, 2019

Switch to using yarn instead of npm
Also stop referencing ./node_modules/.bin/ in package.json scripts
Aaand nuke  from the dev-utils package
Make scripts/ executable in protocol
Also update the version of truffle
Integrate prettier
Also add the eslint-config-pretter to make eslint and prettier compatible.
Also fix some comment wrapping issues by using the Rewrap VSCode extension.
Change npm to brew in README
That is, in the instructions for installing yarn
Rename ACE and ZkAsset folders to ERC1723 and ERCC1724
On top of that, move the contracts ending with Test into the new test folder.
Make sure that the test folder is not published on npm
Create .github folder and set up CODEOWNERS
Add monorepo-wide prettier scripts
Apply prettier to markdown files too
ci: add a semantic release step
also narrow coverage only for @aztec/protocol (this is temporary)

@PaulRBerg PaulRBerg self-assigned this Mar 29, 2019


This comment has been minimized.

Copy link
Collaborator Author

PaulRBerg commented Apr 16, 2019

Closing this as most of the stuff in here is now on the develop branch.

@PaulRBerg PaulRBerg closed this Apr 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.