You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Adding-a-New-API-Version.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
**Document Purpose**: Step-by-step guide for adding support for a new API version (e.g., `v20300101`) to the mx-platform-node repository.
4
4
5
-
**Last Updated**: January 29, 2026
5
+
**Last Updated**: February 18, 2026
6
6
**Time to Complete**: 30-45 minutes
7
7
**Prerequisites**: Familiarity with the multi-version architecture (see [Multi-Version-SDK-Flow.md](Multi-Version-SDK-Flow.md))
8
8
@@ -152,6 +152,8 @@ version_directory:
152
152
153
153
This workflow is automatically triggered by the OpenAPI repository to generate and push SDKs for all versions in parallel.
154
154
155
+
**Note**: The existing infrastructure handles config file artifact upload/download between Generate and Process-and-Push jobs automatically. You only need to add the version-to-config mapping below — the artifact pipeline will pick up your new config file without additional changes.
156
+
155
157
**Location 1: Version-to-config mapping**
156
158
157
159
In the `Setup` job's `Set up matrix` step, find the section with the version-to-config mapping and add an `elif` branch for your new version:
@@ -228,9 +230,11 @@ on:
228
230
- 'v20111101/**'
229
231
- 'v20250224/**'
230
232
- 'v20300101/**' # NEW
233
+
repository_dispatch:
234
+
types: [automated_push_to_master] # No changes needed here
231
235
```
232
236
233
-
This ensures the workflow triggers when changes to your version directory are pushed to master.
237
+
This ensures the workflow triggers when changes to your version directory are pushed to master. The `repository_dispatch` trigger does not need modification — it is used by `openapi-generate-and-push.yml` to trigger this workflow after automated pushes, and works regardless of which version directories changed.
Copy file name to clipboardExpand all lines: docs/Multi-Version-SDK-Flow.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
**Document Purpose**: Quick-reference guide to the multi-version SDK generation, publishing, and release system. This is your entry point to understanding how the system works.
4
4
5
-
**Last Updated**: January 28, 2026
5
+
**Last Updated**: February 18, 2026
6
6
**Read Time**: 5-10 minutes
7
7
**Audience**: Anyone joining the team or needing a system overview
1.`openapi-generate-and-push.yml` generates all specified versions in parallel
39
39
2. All generated files committed to master
40
-
3.`on-push-master.yml`automatically triggered by the push
40
+
3.`openapi-generate-and-push.yml` sends a `repository_dispatch` event (`automated_push_to_master`) to trigger `on-push-master.yml`(required because `GITHUB_TOKEN` pushes don't trigger other workflows)
41
41
4.`on-push-master.yml` handles serial publish/release with version gating
42
42
43
43
**Key Details**: See [Workflow-and-Configuration-Reference.md](Workflow-and-Configuration-Reference.md#flow-1-automatic-multi-version-generation-repository-dispatch)
@@ -83,7 +83,7 @@ sequenceDiagram
83
83
Gen->>Push: Commit to master<br/>Update CHANGELOG.md
0 commit comments