feat: add support for next 16

[strausr]

Description

Issue Ticket Number

Fixes #<ISSUE_NUMBER>

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Fix or improve the documentation
• This change requires a documentation update

Checklist

• I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
• I have created an issue ticket for this PR
• I have checked to ensure there aren't other open Pull Requests for the same update/change?
• I have performed a self-review of my own code
• I have run tests locally to ensure they all pass
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes needed to the documentation

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
next-cloudinary	Ready	Preview	Nov 5, 2025 5:13pm

[PaulBoye-py]

Closing in favour of #657, which implements the same Next.js 16 compatibility cleanly on top of the current main (v6.18.8).

This PR was based on v6.17.1 and is now 30+ commits behind main, including conflicts with the Trusted Publishers release pipeline that was introduced in v6.18.x. The new PR covers the same changes without those issues.

Thanks for the original work on this, as it was used as a reference.