Repository navigation
📦:title dependency updates the way we do - #929
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe Renovate configuration disables semantic commits and adds a custom emoji-prefixed commit message template. Production and development dependency rules retain their labels but no longer set commit message prefixes. ChangesRenovate commit messages
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to Renovate titles now use the requested package format. No concrete validator failure was established as a merge blocker, though other possible overlength updates remain unconfirmed. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Linked Issues checkExplanation Issue
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Renovate titled its pull requests `build(deps-dev): bump all` and `chore(deps): lock file maintenance`, in the Conventional Commits style this organization does not use. Each one lands as a commit on `main` like any other, so the history carried two formats, and the one the bot used is the one the handbook and the checks do not recognize. Its titles and commits now open with the packages category, `📦`, then `:` with no space, then what it did: `📦:bump cspell to v10.3.3`. The semantic prefixes go, along with the preset that set their type and the per-dependency-type prefixes; the labels those rules also set stay. The format is written as the commit message template, because a prefix gets a space after it and every kind of update sets its own action, so neither of the other options can put the emoji first on every update. The template also lowercases the action, which the presets capitalize (`Lock file maintenance`, `Pin`), so every subject starts lowercase like the rest of the history: `📦:lock file maintenance`. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5 Fixes: #184
697de6a to
128f5cc
Compare
Renovate titled its pull requests `build(deps-dev): bump all` and `chore(deps): lock file maintenance`, in the Conventional Commits style this organization does not use. Each one lands as a commit like any other, so the history carried two formats, and the one the bot used is the one the handbook and the checks do not recognize. Its titles and commits now open with the packages category, `📦`, then `:` with no space, then what it did in lowercase: `📦:bump cspell to v10.3.3`, `📦:lock file maintenance`. The semantic prefixes go, along with the preset that set their type and the per-dependency-type prefixes; the labels those rules also set stay. The format is written as the commit message template, because a prefix gets a space after it and every kind of update sets its own action, so neither of the other options can put the emoji first on every update. The template lowercases the action, which the presets capitalize (`Lock file maintenance`, `Pin`), and leaves the package name as it is. This is the change the organization defaults repository made for itself, so all three repositories title dependency updates alike. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5 PR-URL: #1912 Refs: OpenINF/.github#184 Refs: OpenINF/.github#929
Renovate titled its pull requests `build(deps-dev): bump all` and `chore(deps): lock file maintenance`, in the Conventional Commits style this organization does not use. Each one lands as a commit like any other, so the history carried two formats, and the one the bot used is the one the handbook and the checks do not recognize. Its titles and commits now open with the packages category, `📦`, then `:` with no space, then what it did in lowercase: `📦:bump cspell to v10.3.3`, `📦:lock file maintenance`. The semantic prefixes go, along with the preset that set their type and the per-dependency-type prefixes; the labels those rules also set stay. The format is written as the commit message template, because a prefix gets a space after it and every kind of update sets its own action, so neither of the other options can put the emoji first on every update. The template lowercases the action, which the presets capitalize (`Lock file maintenance`, `Pin`), and leaves the package name as it is. This is the change the organization defaults repository made for itself, so all three repositories title dependency updates alike. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5 PR-URL: #76 Refs: OpenINF/.github#184 Refs: OpenINF/.github#929
Requested by DerekNonGeneric
Before: Renovate opened pull requests titled
build(deps-dev): bump allandchore(deps): lock file maintenance, and they landed onmainin that Conventional Commits style.After: they read
📦:bump cspell to v10.3.3and📦:lock file maintenance, the organization's own format with the packages category first and a lowercase subject. Both passvalidateCommitMessage.How:
.renovaterc.json5drops semantic commits, the preset that set their type, and the two per-dependency-type prefixes (their labels stay), and sets the commit message template to start with📦:. The template runs the action through Renovate'slowercasehelper, because its presets capitalize it (Lock file maintenance,Pin,Roll back,Replace); the package name keeps its case. Renovate marks editing that template as deprecated, but it is the only option that can put the emoji flush against the rest for every kind of update.renovate-config-validator44.115.10 accepts the file with that one deprecation warning.Fixes #184
Summary by CodeRabbit