# Context <!-- WHEN CREATED What is the issue that we are seeing that is motivating this decision or change. Give any elements that help understanding where this issue comes from. Leave no room for suggestions or implicit deduction. --> Part of improving the automation of release flow # Decision <!-- WHEN CREATED Give details about the architectural decision and what it is doing. Be extensive: use schemas and references when possible; do not hesitate to use schemas and references when possible. --> Le's use this https://github.com/toitlang/action-macos-sign-notarize # Acceptance Criteria <!-- WHEN CREATED Use standard vocabulary to describe requirement levels RFC-2119: Must-Should-May. e.g. 1. The API _must_ support creation of wallets through a dedicated endpoint. --> --- # Development <!-- WHEN IN PROGRESS In the form of a TODO list, explain how the ticket is going to be tackled and how you intend to proceed. Attach a PR to each point in the list to track progress. e.g. - [ ] I intend to extend the existing handlers and use the wallet layer to implement the necessary steps ==> #123 - [ ] I plan on testing the endpoint by adding a few integration scenarios ==> #456 --> # QA <!-- WHEN IN PROGRESS How are we covering acceptance criteria? Give here manual steps or point to tests that are covering the technical decision we made. -->