Points docs to last stable release #160
Conversation
src/scripts/downloadReleases.js
Outdated
| // TODO: ----------------------------------------------------------------------- debug | ||
| .concat([ | ||
| { | ||
| name: 'v3.0.0-alpha', | ||
| zipball_url: 'https://api.github.com/repos/fastify/fastify/zipball/v1.13.3' | ||
| }, | ||
| { | ||
| name: 'v3.0.0-alpha.2', | ||
| zipball_url: 'https://api.github.com/repos/fastify/fastify/zipball/v1.13.3' | ||
| } | ||
| ]) | ||
| // TODO: ----------------------------------------------------------------------- end of debug |
There was a problem hiding this comment.
Note: This is used to simulate two upcoming alpha release, it will be removed before the merge
lmammino
changed the title
In theory yes, in practice that page might not exist in another version. Not sure right now what would be a better way to handle this to be honest without having to map all the possible pages in advance. |
…st-doc-to-last-stable-release
|
@Eomm, actually, on a second thought, there might be a way to achieve that. The question is,
|
|
I'd make it a follow-up PR. |
|
@jsumners makes sense. Then I will merge this and I will create a dedicated issue to discuss this other potential improvement :) |
Closes #157
This PR changes the current behaviour to point to the
latestdocumentation and provides some high-level refactoring of the build process code.As discussed in #157, the new behaviour is the following:
latestdoesn't track tomasteranymore, the 2 tags are now independentlatestwill point to the most recent version that does not include annotation (as for instance -alpha.1)mastertracks to actualmaster(this is unchanged)I created a fake
v3.0.0-alphato test these assumptions. You can see a preview in the demo below.Please help me to test this thoroughly before we ship any change :)
DEMO: https://latest-doc-to-last-stable-release.surge.sh/