Update manifest.json #2
Conversation
Updates manifest.json current as of 2018-10-25 to reflect latest versions of currently listed repos. This is highly imperfect update (more a bit of a stopgap until vapor/vapor#1827 potential solutions can really be addressed), that takes liberties to: (a) add all `currentmajor.minor` versions, at latest `.patch` point (b) adds a `previousmajor` version, at latest `.minor.patch` point, in a few repos where structure hasn't significantly changed (surely a separation of vapor 2 and vapor 3 documentation entirely, or a thorough reworking by somebody way more familiar with all these major structural changes, would be far superior) (c) removes a few seemingly pointless entries (e.g. RC versions, minor versions at outdated `.patch` levels)
|
The I think what you mean to do here is create a separate file that stores all versions that should be generated. Basically a separate file that could be parsed and used to call The syntax for generating is: ./generate.sh vapor Vapor 3.1.3 |
|
Wow, I must've been really tired when I did this – not only failed to read through the entire flow, but mis-read the parts I did read. 🙄 Just trying to make sure things were up-to-date for when/if the docs did get regen'ed. Oops. |
|
Yeah, currently the workflow is very manual. I run something like: ./generate.sh vapor Vapor 3.1.3I run that one or more times for all of the new tags. Then: ./deployWhich generates the manifest and pushes. It would be nicer if I could add the new tag to some meta-manifest, and then just run |
Updates manifest.json current as of 2018-10-25 to reflect latest versions of currently listed repos.
This is a highly imperfect update (more a bit of a stopgap until vapor/vapor#1827 potential solutions can really be addressed), that takes liberties to:
(a) add all
currentmajor.minorversions, at latest.patchpoint(b) adds a
previousmajorversion, at latest.minor.patchpoint, in a few repos where structure hasn't significantly changed (surely a separation of vapor 2 and vapor 3 documentation entirely, or a thorough reworking by somebody way more familiar with all these major structural changes, would be far superior)(c) removes a few seemingly pointless entries (e.g. RC versions, minor versions at outdated
.patchlevels)