@@ -55,29 +55,33 @@ repo.
5555 - ` version ` key in [ docsy.dev/hugo.yaml]
56564 . Run ` npm run ci:prepare ` to ensure that vendor assets and [ go.mod]
5757 dependencies are up-to-date.
58- 5 . ** Submit a PR with your changes** , using a title like "Release v0.X.Y
58+ 5 . Run ` npm test ` to ensure that all checks pass and the build is successful.
59+ This command runs ` npm run fix ` . Note if there are any file changes, and if
60+ the version ID is still correct and has no build ID (which is usually added
61+ by ` fix:version ` ).
62+ 6 . ** Submit a PR with your changes** , using a title like "Release v0.X.Y
5963 preparation".
60- 6 . ** Test the PR** branch from selected sites, and push any required
64+ 7 . ** Test the PR** branch from selected sites, and push any required
6165 adjustments.
6266 - If the test site uses Docsy as a Git submodule:
63- ``` console
64- $ cd themes/docs
65- $ git fetch
66- $ git switch -t repo/branch-name # e.g. chalin/chalin-im -0.9.1-2024-02-16
67+ ``` sh
68+ cd themes/docs
69+ git fetch
70+ git switch -t REPO/BRANCH-NAME # e.g. chalin/chalin-m25 -0.13.0-dev-alpha
6771 ```
68- 7 . **Get PR approved and merged**.
69- 8 . **Pull in `main`** to get the last PR.
70- 9. **Ensure** that you're:
72+ 8 . ** Get PR approved and merged** .
73+ 9 . ** Pull in ` main` ** to get the last PR.
74+ 10. ** Ensure** that you' re:
7175 - On the default branch, `main`
7276 - At the commit that you want to tag as v0.X.Y
73- 10 . **Create tags** for v0.X.Y:
77+ 11 . **Create tags** for v0.X.Y:
7478
7579 ```sh
7680 REL=v0.X.Y
7781 git tag $REL
7882 ```
7983
80- 11 . **Push the new tags** to the main remote (`origin` or `upstream` depending
84+ 12 . **Push the new tags** to the main remote (`origin` or `upstream` depending
8185 on your setup) as well as any secondary remotes, if any:
8286
8387 ```console
8690 * [new tag] v0.X.Y -> v0.X.Y
8791 ```
8892
89- 12 . **[Draft a new release][]** using GitHub web; fill in the fields as follows:
93+ 13 . **[Draft a new release][]** using GitHub web; fill in the fields as follows:
9094 - From the **release/tag dropdown**: Select the new release tag that you
9195 just pushed, v0.X.Y.
9296 - Set the **release title** to the release number (without the "v").
@@ -104,9 +108,9 @@ repo.
104108
105109 - Select **Create a discussion for this release**.
106110
107- 13 . **Publish the release**: click _Publish release_.
108- 14 . Test the release with a downstream project, such as [docsy-example].
109- 15 . If you find issues, determine whether they need to be fixed immediately. If
111+ 14 . **Publish the release**: click _Publish release_.
112+ 15 . Test the release with a downstream project, such as [docsy-example].
113+ 16 . If you find issues, determine whether they need to be fixed immediately. If
110114 so, get fixes submitted, reviewed and approved. Then publish a dot release:
111115 go back to step 1.
112116
@@ -117,7 +121,7 @@ least one downstream project, then perform the following actions before any
117121further changes are merged into the default branch:
118122
1191231. Set `version` in [package.json] to the next planned (or the next dot) release
120- with a dev suffix, such as `v0.X.Z-dev-unreleased `.
124+ with a dev suffix, such as `v0.X.Z-dev`.
1211252. In the [CHANGELOG]:
122126 - **Create a new entry** for the next release by copying the ENTRY TEMPLATE
123127 at the end of the file.
0 commit comments