This is the code to add a fully automated release process to the crypto library. It's easier to see what is involved in this PR than the incremental way I added it to the library-project-starter.
Roughly it does the following:
user tags HEAD of their master as release-x.y.z when they are ready to release
CircleCI kicks off and runs the .ci-scripts/release.bash script as part of its work it creates a new tag 'x.y.z' that gets pushed
CircleCI gets kicked off my new commits and tag from the previous step
CircleCI generates documentation using upload-release-documentation-to-main-actor.bash which creates the documentation for the release and opens a PR against the repo that the generated-documentation that main.actor uses is stored.
Please let me know here what variables have confusing names, where you would want more comments etc so I can update both this PR and the library-project-starter so we can finalize this and the crypto library can be the first release.
Still to do:
Update the "release process" document to detail how to do this simplified release.
Delete old release.bash that is triggered by hand on a local machine and does far less.
After this is merged and before first release I might add:
Automating the announcement of a new release to the Zulip announcements stream
Automating adding a note about the release to LWIP issue
This is the code to add a fully automated release process to the crypto library. It's easier to see what is involved in this PR than the incremental way I added it to the library-project-starter.
Roughly it does the following:
release-x.y.zwhen they are ready to releaseupload-release-documentation-to-main-actor.bashwhich creates the documentation for the release and opens a PR against the repo that the generated-documentation that main.actor uses is stored.Please let me know here what variables have confusing names, where you would want more comments etc so I can update both this PR and the library-project-starter so we can finalize this and the crypto library can be the first release.
Still to do:
release.bashthat is triggered by hand on a local machine and does far less.After this is merged and before first release I might add: