Updates gem dependencies, handles CVEs, and manages gemspec rules. Use when updating dependencies, checking for outdated gems, or fixing security vulnerabilities.
Attach this file to your Copilot Chat context, then invoke it with the specific dependency update or CVE remediation scope. Apply this workflow before changing version constraints so updates remain consistent with gem project rules.
git.gemspec (both runtime and development) - enforced by RubocopGemfile should remain minimal/empty - do not add dependencies hereGemfile.lock is NOT committed - this is a gem/library projectbundle outdated and bundle audit check --update (if available)git.gemspec if constraints need changing, then run bundle updatebundle exec rake default - must pass on all supported Ruby versions (see CI matrix in .github/workflows/ and minimum version in git.gemspec)fix(deps): update <gem> to fix CVE-XXXX-XXXXchore(deps): update dependencieschore(deps)!: update <gem> with BREAKING CHANGE: footerThis project uses Conventional Commits. A
commit hook enforces the format. See the "Commit message guidelines" section in
CONTRIBUTING.md for the full format and allowed types.
Issue and PR references in the body: Do not use #<number> in the commit
body — write issue 1000 not issue #1000. A commitlint parser flaw treats any
line containing #<number> as a footer token, breaking the body/footer split. To
close an issue/PR, use Closes/Fixes/Resolves #<number> in the footer. To
merely mention one for context, omit the # and no footer line is needed.
To validate a commit message file before committing:
npx commitlint --format @commitlint/format < commit_msg.txt