Final Multi-Version SDK Support Implementation #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Implements Part 5 of the multi-version SDK support for mx-platform-node, enabling the same npm package to publish multiple API versions as independent major versions:
mx-platform-node@2.x.x= API v20111101mx-platform-node@3.x.x= API v20250224Key Changes
Infrastructure Updates
clean.rb,version.rb) for multi-version operations, remove ability to bump major versionpublish.ymlandrelease.ymlworkflowson-push-master.ymlfor parallel version handlingAutomation Improvements
generate.ymlwith version selection dropdown and update bump version to add skip and remove major as optiongenerate_publish_release.ymlwith matrix strategy and add commit SHA support for OAS file retrievalskip-publishsafety flag to prevent spurious publishes during structural changesTemplates & Documentation
package.mustacheto include newapiVersionfield and description for consumer discoveryREADME.mustachewith API version identification sectionMIGRATION.mdwith v20250224 upgrade pathDirectory Structure
latest/→v20111101/to align with semantic versioningTesting
openapirepository dispatch to follow