You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the fields in the file `./packages/__docs__/versions.json` with the latest version and the maintenance branch map. Remove old unsupported versions if they are no longer needed and you don't want them to appear in the docs page version selector.
170
170
171
-
##### 3. Add redirect for the legacy docs
172
-
173
-
Add a new line to the file `./packages/__docs__/_redirects` to redirect the legacy docs. If the current major version is 11, then:
##### 4. Update version references in the docs app
171
+
##### 3. Update version references in the docs app
183
172
184
173
1. In `docs/getting-started/usage.md` update the version in the code snippet for `package.json`
185
174
2. In `packages/__docs__/src/Hero/index.tsx` update the url and title of the Upgrade Guide button
186
175
3. In `packages/__docs__/src/Hero/index.tsx` update the url and title of the Upgrade Guide link in the "What's new?" section
187
176
4. In `packages/__docs__/src/CodeSandboxButton/index.tsx` update the `@instructure/` dependencies to the latest version
188
177
189
-
##### 5. Do a release like it was a minor update
178
+
##### 4. Do a release like it was a minor update
190
179
191
180
Follow the same process as it's described above. The `npm run bump` command should automatically recognise that there were a breaking commit and it should be a major version change.
192
-
193
-
##### 6. Deploy the docs for the maintenance branch
194
-
195
-
Make sure that previous versions of the docs are accessible. If not, deploy them on Netlify using the `Docs deploy to Netlify` GitHub action.
0 commit comments