@@ -61,8 +61,11 @@ When a new version of `melange` is published in opam, a new release of the docs
61
61
and playground should be published. The process is as follows:
62
62
63
63
- Update ` documentation-site.opam ` to point ` melange ` and ` melange-playground `
64
- packages to the commit of the new release
64
+ packages to the commit of the new release (they need to be pinned so that the
65
+ Melange docs can be accessed on a stable path)
65
66
- Update versions of the compiler listed in the playground (` app.jsx ` )
67
+ - In the docs markdown pages, grep for the last version of Melange that was used
68
+ and replace it with the newer one.
66
69
- Open a PR with the changes above
67
70
- After merging the PR, create a new branch ` x.x.x-patches ` . This branch will be
68
71
used to publish any patches or improvements to that version of the docs /
@@ -95,3 +98,8 @@ move-vx.x.x-tag: ## Moves the vx.x.x tag to the latest commit, useful to publish
95
98
- uncomment the relevant code in `publish-version.yml`
96
99
- In the `gh-pages` branch, replace the default version with the new one [in
97
100
index.html](https ://github.com/melange-re/melange-re.github.io/blob/gh-pages/index.html# L10)
101
+ - Finally, we need to disable the publication of previous version `y.y.y` as the
102
+ default version :
103
+ - In `y.y.y-patches` : update `publish-version.yml` so that `mike deploy -push`
104
+ is used and `set-default` is removed.
105
+ - Commit and run `make move-vy.y.y-tag` to deploy
0 commit comments