Pin package versions in Plone buildout versions.cfg files and update changelogs.
npx skills add https://github.com/IMIO/buildout.smartweb --skill pin-package
Please help me install this Agent Skill. Skill: pin-package Source: https://github.com/IMIO/buildout.smartweb/tree/main/.claude/skills/pin-package Command: npx skills add https://github.com/IMIO/buildout.smartweb --skill pin-package
This Skill eliminates the tedious, error-prone manual work of pinning package versions, updating project changelogs, and committing changes in Plone buildout repositories, saving developers significant time during routine dependency management tasks.
Use the pin-package skill to update the version of imio.smartweb.core to 1.4.34 and add its latest changelog entries to the project's CHANGES.rst file.
High-intent search queries and answers about installing and using this skill.
To update package versions in a Plone buildout, this Skill automates editing the versions.cfg file by adding new package versions in correct alphabetical order. It eliminates manual editing errors during routine dependency management tasks.
Yes, you can automatically fetch upstream changelog entries from a package's public GitHub repository. The Skill inserts these entries into your project's CHANGES.rst file under the unreleased section, removing manual copy-pasting work.
For automated Plone dependency pinning, you need access to the project's versions.cfg, CHANGES.rst, and sources.cfg files. Public GitHub access is also required to fetch the upstream changelog data for integration.
Yes, this dependency management workflow is designed for Smartweb and similar Plone projects. When updating core packages like imio.smartweb.core, it handles all file edits and git commits automatically within the buildout repository.
The best way to pin package versions and auto-update changelogs is using an automated Skill that handles versions.cfg updates, extracts GitHub changelog data into CHANGES.rst, and commits the changes. This removes tedious manual copy-pasting and formatting work.
Yes, the Skill handles git commits automatically after updating package versions in versions.cfg and inserting upstream changelog entries into CHANGES.rst. This streamlines the entire dependency update workflow without requiring manual commit steps.
IMIOAutomate Plone buildout upgrades using official release artifacts and generate change reports.
glhewettCommit and push git submodule changes and update the parent repository reference.
Xunzi229Analyze git diffs to update README and CHANGELOG entries.
chrislyonsAutomates release prep with semantic versioning, changelog generation, and GitHub publishing.
