Merge 2.0
Merge 2.0 is a redesigned import workflow that uses a two-phase, two-level diffing engine to identify and apply only what has actually changed in your API spec. Instead of rewriting every section on every import, it compares your new spec against the live state of your project and targets only added, removed, or genuinely modified endpoints - leaving everything else completely untouched.
The result is fewer unintended overwrites, preserved customizations, and a more reliable re-import experience at any scale.
What Gets Preserved
Section IDs on matched endpoints | External links, integrations, and bookmarks to specific sections remain valid after re-import |
Menu structure and ordering | Existing navigation hierarchy is untouched for unchanged and changed sections - only added and removed items modify the menu |
User customizations on unchanged sections | SEO titles, descriptions, display preferences, access control, and viewer lists are never overwritten because unchanged sections are never written to |
Removed section documents | Sections removed from the menu are kept in the database - no content is permanently deleted |
Improved Changelog Accuracy
Because the diff engine knows precisely which endpoints changed and why, the auto-generated Changelog now reflects only real API contract changes. Entries for unchanged sections - which previously appeared as modified due to full re-merge writes - no longer surface in the Changelog. The result is a cleaner, more trustworthy change history with no irrelevant or auto-generated noise.
How to Use Merge 2.0
/ to open the widget menu. Using the CLI
Run the following command:
theneo project import \
--project <project-slug> \
--workspace <workspace-slug> \
--projectVersion <version-slug> \
--publish \
--file ./api-spec.json \
--import-type merge_v2Requirements
- Theneo CLI version 19.1 or later
To verify your CLI version, run:
theneo --version
What made this section helpful for you?
What made this section unhelpful for you?
On this page
- Merge 2.0