plone-update

Automate Plone buildout upgrades using official release artifacts and generate change reports.

5|1|Updated Feb 26, 2021
One-click install
npx skills add https://github.com/IMIO/buildout.smartweb --skill plone-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plone-update
Source: https://github.com/IMIO/buildout.smartweb/tree/main/.claude/skills/plone-update
Command: npx skills add https://github.com/IMIO/buildout.smartweb --skill plone-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating Plone buildout configurations across multiple files and packages is time-consuming and error-prone, especially for deployments like SmartWeb that rely on consistent versioning across core dependencies and custom imio.* packages.

Core Features & Use Cases

  • Official Artifact Validation: Uses only official Plone release artifacts as the source of truth to avoid version mismatches and broken dependencies.
  • Multi-File Automated Updates: Automatically updates root dependency files, buildout configuration files, and imio.* package-specific configs in one workflow.
  • Use Case: A DevOps engineer managing a SmartWeb instance can use this skill to upgrade from Plone 6.1.3 to 6.1.4 across all relevant config files in minutes, with a pre-apply change confirmation and final audit report.

Quick Start

Use the plone-update skill to upgrade this SmartWeb buildout repository to Plone 6.1.4.

Frequently Asked Questions about plone-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Plone buildout configurations to a new target version?

To update Plone buildout configurations, this skill automates upgrading root dependency files, buildout configs, and imio.* package settings to a specified target Plone version. It validates the target against official Plone release artifacts and generates a full change report for review.

What is the safest way to upgrade a SmartWeb buildout repository to Plone 6.1?

The safest way to upgrade a SmartWeb buildout is using official Plone release artifacts as the source of truth. This approach validates the target version, preserves project-specific dependencies, and provides pre-apply change confirmation before modifying root files and imio.* package configs.

Can I use this buildout upgrade process for local authority sites running Plone 6?

Yes, you can use this buildout upgrade process for local authority sites running Plone 6. It is specifically designed for SmartWeb deployment workflows, handling version-consistent updates across core dependencies and custom imio.* packages for stable local authority deployments.

How do official Plone release artifacts prevent version mismatches during a buildout update?

Official Plone release artifacts prevent version mismatches by serving as the single source of truth during the buildout update. The skill validates the requested target version against these artifacts before applying changes, ensuring root dependencies and imio.* package configurations remain synchronized.

Will upgrading Plone buildout configurations overwrite my project-specific dependencies?

Upgrading Plone buildout configurations will not overwrite your project-specific dependencies. The skill explicitly preserves project-specific dependencies while applying version updates to root files and imio.* package configs, providing a pre-apply change confirmation for review.