Claude-skill-registry changelog-pkg
Update pkgsrc ChangeLog entries under config/pkgsrc/files/*/*/ChangeLog and keep Makefile version metadata in sync. Use when updating qrpc-devel or qrpc-prod ChangeLogs, updating their versions, or recording dependency changes.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/changelog-pkg" ~/.claude/skills/majiayu000-claude-skill-registry-changelog-pkg && rm -rf "$T"
manifest:
skills/data/changelog-pkg/SKILL.mdsource content
Changelog Pkg
Overview
Update pkgsrc ChangeLog entries and keep Makefile versions consistent. Only meta-pkgs are reflected in the repository root ChangeLog.
Workflow
- Identify the target package (example:
orqrpc-devel
) underqrpc-prod
and openconfig/pkgsrc/files/<category>/<pkg>/
.config/pkgsrc/files/<category>/<pkg>/ChangeLog - Read the top entry in
and check whether it isChangeLog
.UNRELEASED - Determine the desired next version from the latest released version (first dated entry) and the change type.
- If an
entry exists:UNRELEASED- If its version is lower than the desired next version, update the
line (never lower it).* VERSION: - Update
in the packageDISTNAME
to match the resultingMakefile
version.UNRELEASED - If the ChangeLog includes a
list (meta-pkgs), update it to match the* PACKAGE VERSIONS:
versions in theDEPENDS
and keep the same order.Makefile - Append the new change line(s) under the version list.
- If its version is lower than the desired next version, update the
- If no
entry exists:UNRELEASED- Insert a new
entry at the top with the version line and package list (meta-pkgs only).UNRELEASED - Update
in theDISTNAME
to match the newMakefile
version.UNRELEASED - Add the change line(s) under the list.
- Insert a new
- Do not replace
with a date; only do that at release time.UNRELEASED
Versioning Rules
Use semantic versioning:
- Patch: fixes or small maintenance changes.
- Minor: new features or notable behavior changes.
- Major: breaking changes.
Never downgrade an existing
UNRELEASED version; only raise it when needed.
If an existing
UNRELEASED version is too low for the change (example: 0.1.1 but a feature is added and last release is 0.1.0), update it and sync DISTNAME.
Formatting Rules
Use the existing ChangeLog formatting:
- Use a header line like
orUNRELEASED ts-klassen <qrpc@su-shiki.com>
.YYYY-MM-DD ts-klassen <qrpc@su-shiki.com> - Keep a blank line after the header.
- Use tabs for indentation and
bullets, matching the file.* - Use 2 new lines in between entries.
Root ChangeLog Impact
Only ChangeLogs under
config/pkgsrc/files/meta-pkgs/*/ChangeLog are reflected in the repository root ChangeLog. Other packages (example: config/pkgsrc/files/audio/voicevox_core/ChangeLog) do not trigger a root ChangeLog update.
Example Requests
You will be asked to update the Makefile mainly.
- "Add this package to devel package."
- "Add this package to prod package."
- "Update version of rust-bin package to x.x.x."
Related skills
- changelog-root
- After updating meta-pkgs ChangeLog, update repository root ChangeLog