Release 1.0.0

[alejandrosaenz117]

Pull Request

Release 1.0.0

Types of changes

• A new feature
• A bug fix
• Documentation only changes
• Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• A code change that neither fixes a bug nor adds a feature
• A code change that improves performance
• Adding missing tests or correcting existing tests
• Changes that affect the build system or external dependencies
• Changes to our CI configuration files and scripts
• Other changes that don't modify src or test files

When we released Bulwark to open source, we found bugs that we otherwise would not have found such as creating package.json scripts that worked on windows machines. Furthermore, the documentation has been vastly improved by adding a pull request template, feature template, bug template, and security process template. A Code of Conduct page was also created for our users.

When it comes to the simplicity of starting Bulwark, there was some confusion on how to create the initial Bulwark user. This functionality required an insert to the database or a code change. Instead, a seed function was created to make it easier to create the first user. Additionally, Husky and Commitizen were both implemented to enforce conventional commits.

---

Checklist

• My code follows the contributing guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules

[skewled]

Most of the entries are linting corrections as well as array notation conversion to object notation with member functions. There were no issues spotted when reviewing the changes.