maintenance-release

Automating maintenance releases involves consolidating security advisories and dependency updates into a repeatable workflow. You can gather CVEs, propose scoped update plans, verify changes, bump versions, and prepare GitHub PRs using pnpm.

Planning a maintenance release for multiple CVEs requires gathering security advisories and mapping fixes for affected packages. A structured workflow proposes an update plan, executes targeted pnpm updates, runs build and test verification, and prepares the PR.

Using pnpm to resolve security vulnerabilities starts with running pnpm audit to identify CVEs. After gathering advisories, you execute targeted pnpm updates to patch affected packages, then run pnpm build and pnpm test to verify the changes.

Integrating version bumping and GitHub PR creation into dependency updates is supported by the maintenance release workflow. After verifying updates with pnpm build and test, you invoke versioning workflows and commit changes to create PRs.

Preconditions for a maintenance release workflow include having a clean git tree, being on the main branch, and ensuring the repository is synced. Meeting these conditions ensures a stable base for running pnpm audit and applying dependency updates.

Patching minor and major dependency updates is supported by the dependency update planning feature. The workflow proposes a scoped plan to categorize and apply patch, minor, and major updates across the repository before running verification steps.