...
To create an API version (pre-)release, the API (pre-)release assets need to be created with naming rules as indicated in the below table.
| API |
|---|
| version | API version (OAS file) | API version extension (OAS file) | API version in URL (OAS file) | GitHub tag | GitHub release |
|---|
package (name = tag) | GitHub release package tag |
|---|---|
| initial (x=0) | 0.y.z |
none |
-alpha.m -rc.n | v0.y.z (exception) v0alpham v0rcn | apiname-0.y.z |
apiname-0.y.z-alpha.m apiname-0.y.z |
-rc.n | optional | optional [ pre-release ] |
| alpha | x.y.z | -alpha.m | vxalpham | apiname-x.y.z-alpha.m |
optional |
| optional [ pre-release ] |
| release-candidate | x.y.z | -rc.n | vxrcn | apiname-x.y.z-rc.n |
| mandatory | pre-release | |||
| public-release | x.y.z | none | vx | apiname-x.y.z |
| mandatory | latest | |||||
| work-in-progress | wip | N/A | vwip | N/A | N/A | N/A |
This is illustrated in the following figure:
...