Overview
Following the migration of the Provisioning and Modernization engines to PnP Core SDK (see companion issue), we will be planning a full deprecation of PnP Framework, with the repository moving to public archive status.
We want to be transparent and give the community as much lead time as possible. We are planning to complete the migration to PnP Core SDK over the 2nd quarter of 2027 - one year from now.
Why are we doing this?
PnP Framework has served the community incredibly well as the successor to PnP-Sites-Core. However, PnP Core SDK is the natural evolution: it is modern, cross-platform, and built to last. Maintaining two overlapping libraries is not sustainable, and consolidating everything into PnP Core SDK means a better, more focused experience for everyone going forward.
This decision is not made lightly. It is the result of extensive community discussion and a commitment to doing this the right way - with a long, well-communicated transition window.
What will happen?
What does "archived" mean?
The repository will remain fully accessible and readable. Your existing code will not stop working overnight. Archiving simply means no new changes will be made to PnP Framework - all active development will have moved to PnP Core SDK.
What should you do?
- Start planning your migration now.
- Review the PnP Core SDK documentation to understand the new APIs.
- Follow the phased approach: migrate Provisioning/Modernization first
- Engage with the community - we will provide guidance, migration docs, and support throughout this process.
Thank you for being part of this journey. We are fully committed to making this an easy, well-supported transition. 💙
This is Phase 2 of the PnP Framework deprecation roadmap. See the companion issue for Phase 1: Provisioning and Modernization migration.
Overview
Following the migration of the Provisioning and Modernization engines to PnP Core SDK (see companion issue), we will be planning a full deprecation of PnP Framework, with the repository moving to public archive status.
We want to be transparent and give the community as much lead time as possible. We are planning to complete the migration to PnP Core SDK over the 2nd quarter of 2027 - one year from now.
Why are we doing this?
PnP Framework has served the community incredibly well as the successor to PnP-Sites-Core. However, PnP Core SDK is the natural evolution: it is modern, cross-platform, and built to last. Maintaining two overlapping libraries is not sustainable, and consolidating everything into PnP Core SDK means a better, more focused experience for everyone going forward.
This decision is not made lightly. It is the result of extensive community discussion and a commitment to doing this the right way - with a long, well-communicated transition window.
What will happen?
What does "archived" mean?
The repository will remain fully accessible and readable. Your existing code will not stop working overnight. Archiving simply means no new changes will be made to PnP Framework - all active development will have moved to PnP Core SDK.
What should you do?
Thank you for being part of this journey. We are fully committed to making this an easy, well-supported transition. 💙
This is Phase 2 of the PnP Framework deprecation roadmap. See the companion issue for Phase 1: Provisioning and Modernization migration.