Skip to content

release check list

Prasanth edited this page Dec 13, 2023 · 11 revisions

Lets say we want to release new version of dothttp (M.m.pa1). you will also want to update all dependent versions (dothttp-wasm, dotextensions-build, dothttp-runner, dothttp-playground)

Following docs explain versioning process above repos and actions to take. versions of dothttp will look like M.m.pa1 where M denotes major version, m denotes minor version, p denotes patch version, a denotes alpha (kind of prerelease) and 1 denotes number of prereleases.

dothttp

https://github.com/cedric05/dothttp

https://blog.marcnuri.com/triggering-github-actions-across-different-repositories/

dothttp-wasm

https://github.com/cedric05/dothttp-wasm/

dotextensions-build

https://github.com/cedric05/dotextensions-build

dothttp-runner

https://github.com/cedric05/dothttp-runner

dothttp-runner dependency update dothttp

https://github.com/cedric05/dothttp-runner/blob/VERSION/version.json

  • get urls from #dotextensions-build add new entry
  • update

dothttp-docs

https://github.com/cedric05/dothttp-docs

  • update docs and release announcement

dothttp-playground

https://github.com/cedric05/dothttp-playground

dotbook

https://github.com/cedric05/dotbook

  • release dotbook