0.0.11 release (#24)

* tweak release instructions, bump runtime and builder to latest versions.

.github/maintainers_guide.md

@@ -31,7 +31,7 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
   - Local integration tests between the Slack CLI, deno-sdk-based application template(s) and this repo. One can modify a deno-sdk-based app project's `slack.json` file to point the `get-hooks` hook to a local version of this repo rather than the deno.land-hosted version.
 3. Bump the version number for this repo in adherence to [Semantic Versioning][semver] in `src/version.ts`.
   - Make a single commit with a message for the version bump.
-4. Send a pull request with this change and tag @slack/HDX and/or @filmaj for review.
+4. Send a pull request with this change and tag @slackapi/HDX and/or @slackapi/denosaurs for review.
 5. Once approved and merged, a deployment workflow will kick off. This workflow will:
   - Create a `git` tag matching the version string you changed in `src/version.ts`.
   - Create a new GitHub Release (initially set to a pre-release) for the version.

src/libraries.ts

@@ -7,8 +7,8 @@ export const DENO_SLACK_HOOKS = "deno_slack_hooks";
 export const DENO_SLACK_RUNTIME = "deno_slack_runtime";
 
 export const VERSIONS = {
-  [DENO_SLACK_BUILDER]: "0.0.13",
-  [DENO_SLACK_RUNTIME]: "0.0.7",
+  [DENO_SLACK_BUILDER]: "0.0.14",
+  [DENO_SLACK_RUNTIME]: "0.0.9",
   [DENO_SLACK_HOOKS]: hooksVersion,
 };
 

src/version.ts

@@ -1,4 +1,4 @@
-const VERSION = "0.0.10";
+const VERSION = "0.0.11";
 export default VERSION;
 
 if (import.meta.main) {