mirror of
https://github.com/community-scripts/ProxmoxVE.git
synced 2026-08-25 22:05:42 +02:00
Michel Roegl-Brunner
803fbfdd9f
Explains the ```breaking-change block a breaking-change PR can carry — severity, action (warn/block), expect, and before_update steps — with a copy-paste example kept inside an HTML comment so it stays inert until an author fills it in. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TFBuZEp142Ei2PAfWqbMXT
3.4 KiB
Generated
3.4 KiB
Generated
✍️ Description
🔗 Related Issue
Fixes #
✅ Prerequisites (X in brackets)
- Self-review completed – Code follows project standards.
- Tested thoroughly – Changes work as expected.
- No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.
🤖 AI Assistance (X in brackets)
If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.
- No AI used – Scripts were written without AI assistance.
- AI was used – I confirm the scripts were built using
AGENTS.mdand.github/agents/pve-script-creator.agent.mdas guidance, and the output has been reviewed and corrected to match those guidelines.
🛠️ Type of Change (X in brackets)
- 🐞 Bug fix – Resolves an issue without breaking functionality.
- ✨ New feature – Adds new, non-breaking functionality.
- 💥 Breaking change – Alters existing functionality in a way that may require updates.
- 🆕 New script – A fully functional and tested script or script set.
- 🌍 Website update – Changes to script metadata (PocketBase/website data).
- 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
- 📝 Documentation update – Changes to
README,AppName.md,CONTRIBUTING.md, or other docs.
💥 Breaking Change Advisory (only if you checked "Breaking change")
If this PR changes existing behaviour in a way that may require action before an
update, add a breaking-change advisory block to this PR body. The website and
the in-container update guard read it to tell operators exactly what to expect,
what to do first, and — with action: block — to stop an update until it's
handled. Every field is optional; the advisory auto-expires 30 days after merge.
Copy the block out of the comment below, fill it in, and paste it here: