chore: pin CI to TLibs main and drop stale PR template note - #44
Conversation
The setup-plugins action was pinned to 4f7a354, the head of TLibs PR #19, which is not on any TLibs branch. Pin it to 8ef41de on TLibs main. The action is unchanged; its installer catalogue now also lists GemInfusion. Drop -P'!deploy-live'. No POM defines a deploy-live profile, so the flag does nothing. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
plugin.yml takes its version from the POM through resource filtering, and release versions come from tags, so the two no longer drift. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
|
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: Advanced Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe Maven build and release workflows now use a different plugin-dependencies action pin. Their Maven commands no longer explicitly disable the ChangesMaven workflow updates
Pull request template
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Merge Risk: ⚪ Minimal · up to The workflow changes have no identified build regression, and the template edit removes advisory guidance without establishing a concrete failure. The PR appears ready subject to normal checks. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the build tonight Comment |
Summary
TF-Minecraft/TLibs/.github/actions/setup-pluginsto8ef41deon TLibsmain. The previous pin,4f7a354, is the head of TLibs PR Unify plugin artifact naming, validation, and ignore rules #19 and is not on any branch (Unify plugin artifact naming, validation, and ignore rules #19 was squash-merged as8f48e6f). The action itself is unchanged; since then the installer has only dropped its unused--assetsoption and added GemInfusion to its catalogue.-P'!deploy-live'from the Maven commands. No POM defines adeploy-liveprofile, so the flag does nothing.plugin.yml/pom.xmlversion drift note.plugin.ymlis filtered from the POM and release versions come from tags.Verification
🤖 Generated with Claude Code
Summary by CodeRabbit