Skip to content

Test PR: Changelog: October, November, December 25#5500

Open
SapneshNaik wants to merge 5 commits intoNangoHQ:masterfrom
SapneshNaik:CON-6/backfill-product-updates
Open

Test PR: Changelog: October, November, December 25#5500
SapneshNaik wants to merge 5 commits intoNangoHQ:masterfrom
SapneshNaik:CON-6/backfill-product-updates

Conversation

@SapneshNaik
Copy link
Collaborator

@SapneshNaik SapneshNaik commented Feb 23, 2026

TEST PR: Do not merge

Added Changelog update for October, November 2025.


Add Oct–Dec 2025 changelog content & assets

Expands docs/updates/product.mdx with three new changelog entries for October, November, and December 2025 covering newly supported APIs, product highlights (connection tags, OAuth error UX, integrations UI, CLI updates, testing guidance), and monthly blog links. Adds one new screenshot asset (docs/images/changelog/Nango_CLI_interactive_mode.png) and reuses several existing media files referenced from the new sections.

Key Changes

• Prepended a December 2025 update describing 22 new APIs, connection tags, OAuth callback improvements, integrations UX redesign, and December blog posts.
• Inserted a November 2025 update with 27 APIs, advanced connection settings, CLI template cloning/dependency management, mock file restructuring, CI/CD guidance placeholder, and November blog links.
• Inserted an October 2025 update featuring 23 APIs, CLI interactive mode (with new screenshot), mock file guidance, CI/CD link, and October blog posts.
• Added supporting screenshot docs/images/changelog/Nango_CLI_interactive_mode.png referenced by the October CLI section.

Possible Issues

• Broken November blog URLs (currently pointing to notion.so instead of nango.dev).
• Improperly formatted code block for nango create --sync --integration my-api --name get-contacts, causing MDX rendering issues.
• Lingering word test and sentence fragment degrade readability and could confuse readers.
• Potential broken image if relative path is incorrect in the built site.


This summary was automatically generated by @propel-code-bot

propel-code-bot[bot]

This comment was marked as outdated.

@SapneshNaik SapneshNaik changed the title Test PR: Changelog: October 25 Test PR: Changelog: October, November 25 Feb 23, 2026
Copy link
Contributor

@propel-code-bot propel-code-bot bot left a comment

Choose a reason for hiding this comment

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

Documentation entry needs minor edits for clarity and brand accuracy.

Status: Minor Suggestions | Risk: Low

Issues Identified & Suggestions
  • Fix sentence fragment and proper noun capitalization: docs/updates/product.mdx
Review Details

📁 2 files reviewed | 💬 2 comments

Instruction Files
├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

👍 / 👎 individual comments to help improve reviews for you

- [Rocketlane](/integrations/all/rocketlane)
- [Prospeo](/integrations/all/prospeo)
- [PracticeFusion](/api-integrations/practicefusion)
- [Semrush (v3)](/integrations/all/semrush)
Copy link
Contributor

Choose a reason for hiding this comment

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

Advisory

[Documentation] Fix proper noun capitalization: "Shipstation" should be spelled "ShipStation".

Context for Agents
[**Documentation**]

Fix proper noun capitalization: "Shipstation" should be spelled "ShipStation".

File: docs/updates/product.mdx
Line: 30

@SapneshNaik SapneshNaik changed the title Test PR: Changelog: October, November 25 Test PR: Changelog: October, November, December 25 Feb 23, 2026
Copy link
Contributor

@propel-code-bot propel-code-bot bot left a comment

Choose a reason for hiding this comment

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

One important issue remains: November changelog blog links still point to the wrong domain.

Status: Changes Suggested | Risk: Medium

Issues Identified & Suggestions
  • November blog links misdirect to Notion instead of Nango site: docs/updates/product.mdx
Review Details

📁 2 files reviewed | 💬 1 comments

Instruction Files
├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

👍 / 👎 individual comments to help improve reviews for you

Comment on lines +104 to +106
- [How to build integrations you and your customers love](https://www.notion.so/blog/how-to-build-integrations-you-and-your-customers-love)
- [The hidden costs of building product integrations in-house](https://www.notion.so/blog/the-hidden-costs-of-building-product-integrations-in-house)
- [Product integrations: Build or buy?](https://www.notion.so/blog/product-integrations-build-or-buy)
Copy link
Contributor

Choose a reason for hiding this comment

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

Important

[Logic] All other months in this changelog reference Nango blog posts under https://www.nango.dev/blog/..., but the three November entries here point to notion.so. That sends readers to the wrong site and breaks the navigation goal called out in the PR description. Please update these URLs to the Nango blog domain so they resolve correctly.

Suggested change
- [How to build integrations you and your customers love](https://www.notion.so/blog/how-to-build-integrations-you-and-your-customers-love)
- [The hidden costs of building product integrations in-house](https://www.notion.so/blog/the-hidden-costs-of-building-product-integrations-in-house)
- [Product integrations: Build or buy?](https://www.notion.so/blog/product-integrations-build-or-buy)
- [How to build integrations you and your customers love](https://www.nango.dev/blog/how-to-build-integrations-you-and-your-customers-love)
- [The hidden costs of building product integrations in-house](https://www.nango.dev/blog/the-hidden-costs-of-building-product-integrations-in-house)
- [Product integrations: Build or buy?](https://www.nango.dev/blog/product-integrations-build-or-buy)
Context for Agents
All other months in this changelog reference Nango blog posts under `https://www.nango.dev/blog/...`, but the three November entries here point to `notion.so`. That sends readers to the wrong site and breaks the navigation goal called out in the PR description. Please update these URLs to the Nango blog domain so they resolve correctly.

```suggestion
- [How to build integrations you and your customers love](https://www.nango.dev/blog/how-to-build-integrations-you-and-your-customers-love)
- [The hidden costs of building product integrations in-house](https://www.nango.dev/blog/the-hidden-costs-of-building-product-integrations-in-house)
- [Product integrations: Build or buy?](https://www.nango.dev/blog/product-integrations-build-or-buy)
```


File: docs/updates/product.mdx
Line: 106

Copy link
Contributor

@propel-code-bot propel-code-bot bot left a comment

Choose a reason for hiding this comment

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

Minor doc polish needed to clean up the CLI example formatting and prose.

Status: Minor Suggestions | Risk: Low

Issues Identified & Suggestions
  • Correct stray "test" wording and render CLI command in its own fenced block: docs/updates/product.mdx
Review Details

📁 2 files reviewed | 💬 2 comments

Instruction Files
├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

👍 / 👎 individual comments to help improve reviews for you


The Nango CLI now supports an [interactive mode](https://nango.dev/docs/reference/cli#interactive-mode) that prompts for missing arguments. For example, run `nango create` without specifying the function type, integration, or name, and the CLI will ask for them. Interactive mode is on by default in interactive terminal sessions.

![Nango_CLI_interactive_mode](../images/changelog/Nango_CLI_interactive_mode.png)
Copy link
Contributor

Choose a reason for hiding this comment

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

Advisory

[Documentation] Remove the stray word “test” and move the nango create --sync --integration my-api --name get-contacts command onto its own fenced code block (put the command on a new line after the opening and before the closing). As written, the command is treated as the fence’s language spec and the example doesn’t render.

Context for Agents
[**Documentation**]

Remove the stray word “test” and move the `nango create --sync --integration my-api --name get-contacts` command onto its own fenced code block (put the command on a new line after the opening ``` and before the closing ```). As written, the command is treated as the fence’s language spec and the example doesn’t render.

File: docs/updates/product.mdx
Line: 140


![Nango_CLI_interactive_mode](../images/changelog/Nango_CLI_interactive_mode.png)

You can still provide all arguments upfront to skip prompts (e.g., for scripting): test
Copy link
Contributor

Choose a reason for hiding this comment

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

Advisory

[Documentation] The stray word test after the colon makes the sentence read oddly and suggests the command is itself a test string. Dropping it keeps the prose clean while still introducing the code sample below.

Suggested change
You can still provide all arguments upfront to skip prompts (e.g., for scripting): test
You can still provide all arguments upfront to skip prompts (e.g., for scripting):
Context for Agents
The stray word `test` after the colon makes the sentence read oddly and suggests the command is itself a test string. Dropping it keeps the prose clean while still introducing the code sample below.
```suggestion
You can still provide all arguments upfront to skip prompts (e.g., for scripting):
```

File: docs/updates/product.mdx
Line: 142

Copy link
Contributor

@propel-code-bot propel-code-bot bot left a comment

Choose a reason for hiding this comment

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

No issues found; the changelog updates, assets, and links appear compliant and ready to merge.

Status: No Issues Found | Risk: Low

Review Details

📁 6 files reviewed | 💬 0 comments

Instruction Files
├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

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.

2 participants