π Summary
This release (v0.0.48) improves handling of HTTP errors during URL validation by introducing a centralized mechanism for managing bad status codes. This update enhances code maintainability, increases reliability, and provides clearer functionality. ππ
π Key Changes
- π οΈ Introduced a `BAD_HTTP_CODES` frozenset to consolidate and manage HTTP error codes used in URL validation (e.g., 404, 500, 503).
- π Replaced hardcoded error codes throughout the codebase with the new `BAD_HTTP_CODES` construct.
- π’ Bumped the version from 0.0.47 to 0.0.48 for clarity in tracking updates.
π― Purpose & Impact
- π§Ή **Cleaner Code**: Centralizing error codes into a single reusable frozenset improves maintainability and ensures consistency across the project.
- π‘οΈ **Improved Reliability**: By addressing a broader range of HTTP errors (e.g., 403, 410), URL validation now accounts for additional scenarios, reducing potential failures or false positives.
- π **User-Focused Improvements**: Developers benefit from a robust and reliable URL-checking mechanism that is easier to understand and adapt for different applications.
This update ensures better management of HTTP error handling, paving the way for more effective and user-friendly integrations. β
What's Changed
* Add 403 and 410 http error codes by glenn-jocher in https://github.com/ultralytics/actions/pull/382
**Full Changelog**: https://github.com/ultralytics/actions/compare/v0.0.47...v0.0.48