docs: include reference to rebuilding docs after a release

zimeg · zimeg · commit 40cd59e9c948 · 2025-07-09T17:11:55.000-07:00
diff --git a/.github/maintainers_guide.md b/.github/maintainers_guide.md
@@ -61,7 +61,8 @@ $ git push -u origin v1.2.3
 ```
 
 6. After merging these changes into `main` create a new [release](https://github.com/slackapi/slack-github-action/releases/new) with a new tag - `v1.2.3` - on publish. Include relevant changes in the release notes!
-7. Once released, make sure to close the relevant GitHub Milestone for the version you released.
+7. Rebuild [documentation](#docs) with the latest versions.
+8. Once released, make sure to close the relevant GitHub Milestone for the version you released.
 
 ## Workflow
 
@@ -118,19 +119,19 @@ This repo contains two types of docs files:
 
 The private repo containing the tools.slack.dev site pulls these in at build time.
 
-Maintainers need to use the `run workflow` button associated with the `deploy` workflow in that private repo  to update the docs with changes from here. 
+Maintainers need to use the `run workflow` button associated with the `deploy` workflow in that private repo to update the docs with changes from here.
 
 ### Markdown Files
 
 The markdown files here are secretly mdx files in disguise.
 
 If you'd like to add images to pages, add the image files to the same folder the md file is in.
 
-We appreciate markdown edits from anyone!!! 
+We appreciate markdown edits from anyone!!!
 
 ### Sidebar
 
-`_sidebar.json` sets the slack github action docs sidebar 
+`_sidebar.json` sets the slack github action docs sidebar
 
 sidebar values take the form of "slack-github-action/path-within-docs/"
 
