Skip to content

Conversation

codebrain
Copy link
Contributor

@codebrain codebrain commented Jan 30, 2019

This pull request addresses an issue whereby the documentation can be generated for a release with the incorrect version number. The version number is now calculated from the global.json file, thereby limiting the chances of the incorrect version number being used on a release.

Regular expressions and basic character manipulation has been used to avoid the need for JSON parsing and Semver libraries.

Backport to 6.x on merge.

Copy link
Member

@Mpdreamz Mpdreamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brute force 😄 LGTM

@russcam russcam merged commit 85cdf95 into master Mar 5, 2019
russcam pushed a commit that referenced this pull request Mar 5, 2019
@russcam
Copy link
Contributor

russcam commented Mar 5, 2019

ported to 6.x: 3b9cde8
ported to 5.x: 4e08047

russcam pushed a commit that referenced this pull request Mar 5, 2019
@russcam russcam deleted the feature/use-global-json-in-docs branch March 28, 2019 02:52
russcam pushed a commit that referenced this pull request Apr 3, 2019
…g documentation. (#3557)

(cherry picked from commit 85cdf95)
(cherry picked from commit 3b9cde8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants