Agent skill · software engineering · jeremylongshore
documenso-upgrade-migration
Manage Documenso API version upgrades and SDK migrations.
Why this skill is useful
Adds executable scripts and detailed migration patterns for upgrading between Documenso API versions that are not publicly documented.
What it needs
Requires npm, pip installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Documenso Upgrade & Migration Output A versioned upgrade record with compatibility, access/audit checks, staged evidence, and a verified rollback revision. A paused/reversible release decision when any signing, authorization, or retention requirement regresses. Examples Upgrade in a development workspace using synthetic documents and signers, test the previous and target versions for lifecycle, callback, access, and audit behavior, then stage a canary. Retain the prior release/configuration and roll back immediately if a control fails; do not validate upgrades by changing live signed documents. Current State !npm list @documenso/sdk-typescript 2>/dev/null echo 'SDK not installed' !npm list documenso-sdk-python 2>/dev/null pip show documenso-sdk-python 2>/dev/null head -3 echo 'Python SDK not installed' Overview Guide for upgrading between Documenso API versions and SDK updates. Documenso has two API versions: v1 (legacy, document-centric) and v2 (recommended, envelope-based with multi-document support). The TypeScript and Python SDKs use the v2 API by default. Prerequisites Current Documenso integration working Test environment available Feature flag system (recommended for gradual rollout) API Version Comparison Feature v1 (legacy) v2 (recommended) --------- ------------- ------------------- Base path /api/v1/ /api/v2/ Document model Documents Envelopes (can contain multiple documents) SDK support REST only TypeScript + Python SDK Template API /templates/{id}/create-document Via envelope create Authentication Authorization: Bearer Authorization: Bearer (same) Status Maintained, not deprecated Actively developed Instructions Step 1: Upgrade SDK to Latest Step 2: v1 REST to v2 SDK Migration Step 3: Gradual Migration with Feature Flags Step 4: Self-Hosted Version Upgrade Step 5: Migration Testing Migration Checklist [ ] Current SDK version documented [ ] Changelog reviewed for breaking changes [ ] Feature branch created for migration [ ] v2 SDK installed alongside v1 …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/documenso-upgrade-migration