miro-upgrade-migration

Featured

Migrate Miro integrations from REST API v1 to v2 and upgrade @mirohq/miro-api SDK. Use when upgrading SDK versions, migrating v1 widget endpoints to v2 item endpoints, or handling breaking changes in the Miro platform. Trigger with phrases like "upgrade miro", "miro migration", "miro v1 to v2", "update miro SDK", "miro breaking changes".

API & Backend 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Miro Upgrade & Migration ## Overview Guide for migrating from Miro REST API v1 to v2, upgrading the `@mirohq/miro-api` SDK, and handling the key breaking changes between versions. ## Key Breaking Changes: v1 to v2 ### Terminology Changes | v1 Term | v2 Term | Notes | |---------|---------|-------| | Widget | Item | All board elements renamed | | Line | Connector | Lines renamed, gained captions and snapTo | | Sticker | Sticky Note | Type value: `sticky_note` | | Widget API (polymorphic) | Per-type endpoints | No more universal create endpoint | | `text` property | `content` property | In data objects | | `shapeType` | `shape` (in `data`) | Moved from style to data object | | `startWidget` / `endWidget` | `startItem` / `endItem` | Connector endpoints | | Board User Connection | Board Member | Sharing/permissions model | ### Endpoint Migration Map ``` # v1 (DEPRECATED) → v2 (CURRENT) POST /v1/boards/{id}/widgets → POST /v2/boards/{id}/sticky_notes POST /v2/boards/{id}/shapes POST /v2/boards/{id}/cards POST /v2/boards/{id}/texts POST /v2/boards/{id}/frames POST /v2/boards/{id}/images POST /v2/boards/{id}/documents PO...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

miro-migration-deep-dive

Execute major Miro migrations — migrate boards between teams/orgs, export board content to external systems, import data into Miro, and re-platform from competing whiteboard tools using REST API v2. Trigger with phrases like "migrate miro", "miro migration", "export miro boards", "import to miro", "miro data migration".

2,266 Updated today
jeremylongshore
AI & Automation Solid

webflow-upgrade-migration

Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".

2,266 Updated today
jeremylongshore
AI & Automation Featured

cohere-upgrade-migration

Migrate from Cohere API v1 to v2 and upgrade SDK versions. Use when upgrading cohere-ai SDK, migrating from CohereClient to CohereClientV2, or handling breaking changes between API versions. Trigger with phrases like "upgrade cohere", "cohere migration", "cohere v1 to v2", "update cohere SDK", "cohere breaking changes".

2,266 Updated today
jeremylongshore
API & Backend Featured

instantly-upgrade-migration

Migrate Instantly.ai integrations from API v1 to v2. Use when upgrading from deprecated v1 endpoints, updating authentication, or migrating endpoint paths and request formats. Trigger with phrases like "instantly v1 to v2", "instantly api migration", "instantly upgrade", "instantly deprecated", "migrate instantly api".

2,266 Updated today
jeremylongshore
AI & Automation Featured

klaviyo-upgrade-migration

Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like "upgrade klaviyo", "klaviyo migration", "klaviyo breaking changes", "update klaviyo SDK", "klaviyo API revision".

2,266 Updated today
jeremylongshore