Limitations and Unsupported Features
Known limitations and unsupported configuration options for Dependabot on Azure DevOps.
While Paklo aims to support all official Dependabot configuration options, there are some limitations specific to Azure DevOps and the different deployment methods.
Feature Parity Status
| Feature | Extension (v2) | Hosted | CLI |
|---|---|---|---|
| Basic updates | ✅ | ✅ | ✅ |
| Security-only updates | ✅ | ✅ | ✅ |
| Private registries | ✅ | ✅ | ✅ |
| Custom CA certificates | ✅ | ❌ | ✅ |
| Experiments | ✅ | ⚠️ Partial | ✅ |
| Groups | ✅ | ✅ | ✅ |
| Assignees | ✅ | ✅ | ✅ |
| Labels | ✅ | ✅ | ✅ |
| Milestones | ✅ | ✅ | ✅ |
| Custom commit messages | ✅ | ✅ | ✅ |
| Ignore rules | ✅ | ✅ | ✅ |
| Allow rules | ✅ | ✅ | ✅ |
| Target branch | ✅ | ✅ | ✅ |
| Rebase strategy | ✅ | ✅ | ✅ |
| Vendor (Go) | ✅ | ✅ | ✅ |
| Version strategy | ✅ | ✅ | ✅ |
Legend:
- ✅ Fully supported
- ⚠️ Partially supported or with limitations
- ❌ Not supported
Reporting Issues
If you encounter limitations not documented here:
- Check if it's a known issue in GitHub Issues
- Search Discussions for workarounds
- Create a new issue with:
- Your deployment method (extension, hosted, or CLI)
- The feature or configuration that doesn't work
- Your
dependabot.ymlconfiguration (sanitized) - Any error messages or logs
How is this guide?
Last updated on