ci(release): automate the release-process by using the release-please…

… bot (#79)

.github/workflows/release-please.yml

@@ -0,0 +1,18 @@
+name: release-please
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v3
+        with:
+          command: manifest

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.10.0"
+}

CONTRIBUTING.md

@@ -0,0 +1,9 @@
+# Contributor Guide
+
+## Commit Messages
+
+Because we use the [release-please](https://github.com/googleapis/release-please) bot, commit messages to main must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. This is enforced by the [commitlint](https://commitlint.js.org/#/) tool. This requirement is only enforced on the `main` branch. Commit messages in PRs can be whatever you want them to be. "Squash" mode must be used when merging a PR, with a commit message that follows the Conventional Commits specification.
+
+## Release Process
+
+This repo uses the [release-please](https://github.com/googleapis/release-please) bot. Release-please will automatically open a PR to update the version of the repo when a commit is merged to `main` that follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. The bot will automatically keep the PR up to date until a human merges it. When that happens the bot will automatically create a new release.

README.md

@@ -4,6 +4,8 @@ Build Harness is a Docker image, loaded with an array of tools, built to transfo
 
 ## Getting Started
 
+### Using Build Harness
+
 Getting started with Build Harness is as easy as running `docker run`. Here's an example from the perspective of how somebody might use it in a setting where a Golang application is being developed.
 
 ```
@@ -25,6 +27,10 @@ Doing so would allow running the same command (`make test`) in your local enviro
 
 To get a better idea of what it looks like to use Build Harness operationally, take a look at [this repo](https://github.com/defenseunicorns/terraform-aws-uds-vpc) where it is used. This pattern uses a Makefile to wrap actions that utilize Build Harness to run `make test` or `make pre-commit-all`.
 
+### Contributing to Build Harness
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for more information on how to contribute to Build Harness.
+
 ## Why Repeatable Environments?
 
 In an increasingly complex and distributed development landscape, the ability to have consistent and repeatable build and test environments has become a non-negotiable requirement. A common baseline ensures code behaves the same way across all settings, eliminating the infamous "it works on my machine" scenarios. Having a consistent environment reduces the time spent troubleshooting environment-specific issues and allows teams to focus on what really matters - building great software.

release-please-config.json

@@ -0,0 +1,39 @@
+{
+  "packages": {
+    ".": {
+      "bump-minor-pre-major": true,
+      "bump-patch-for-minor-pre-major": true,
+      "changelog-host": "https://github.com",
+      "changelog-path": "CHANGELOG.md",
+      "changelog-sections": [
+        { "type": "feat", "section": "Features" },
+        { "type": "feature", "section": "Features" },
+        { "type": "fix", "section": "Bug Fixes" },
+        { "type": "perf", "section": "Performance Improvements" },
+        { "type": "revert", "section": "Reverts" },
+        { "type": "docs", "section": "Documentation" },
+        { "type": "style", "section": "Styles" },
+        { "type": "chore", "section": "Miscellaneous Chores" },
+        { "type": "refactor", "section": "Code Refactoring" },
+        { "type": "test", "section": "Tests" },
+        { "type": "build", "section": "Build System" },
+        { "type": "ci", "section": "Continuous Integration" }
+      ],
+      "changelog-type": "default",
+      "draft": false,
+      "draft-pull-request": false,
+      "exclude-paths": [],
+      "extra-files": [],
+      "extra-label": "",
+      "include-component-in-tag": false,
+      "include-v-in-tag": false,
+      "prerelease": false,
+      "pull-request-header": ":robot: I have created a release *beep* *boop*",
+      "pull-request-title-pattern": "chore${scope}: release ${component} ${version}",
+      "release-type": "simple",
+      "separate-pull-requests": false,
+      "skip-github-release": false,
+      "versioning": "default"
+    }
+  }
+}