v0.0.87 - Update common_utils.py to fix extra trailing backslash (#478)

🌟 Summary

This release improves URL handling for greater reliability and streamlines code quality checks, making the development process smoother and more accurate. 🚀🔗

📊 Key Changes

• Enhanced URL validation logic: URLs are now only updated if a real HTTP redirect occurs, reducing unnecessary changes.
• Updated the package version to 0.0.87 for easier tracking of improvements.
• Added "finalY" to the codespell ignore list to prevent it from being incorrectly flagged as a spelling error.

🎯 Purpose & Impact

• 🛡️ Boosts reliability in automated URL checks, ensuring only genuine redirects update URLs—helpful for users relying on precise URL validation.
• 🧹 Reduces false-positive spelling errors, making code reviews and automated checks less disruptive for developers.
• 📈 The version bump helps users and teams quickly identify and benefit from these improvements.

What's Changed

• Ignore finalY for spelling (X and Y axes) by @glenn-jocher in #477
• Update common_utils.py to fix extra trailing backslash by @glenn-jocher in #478

Full Changelog: v0.0.86...v0.0.87

v0.0.86 - Robust summarize_release.py previous tag (#475)

🌟 Summary

This release strengthens the reliability of release automation and testing workflows, making the process more robust and error-resistant for both developers and users. 🛡️✨

📊 Key Changes

• Improved the release summary script to handle API errors and missing data more gracefully, reducing the chance of failures during automated releases.
• Enhanced logic for identifying previous Git tags, ensuring accurate release comparisons even in edge cases.
• Expanded and updated automated tests for both release and file update scripts, including real-file and edge-case scenarios.
• Upgraded Slack notification actions to the latest version for better error messages and configuration options.
• Increased overall test coverage for file header and markdown code block update scripts.

🎯 Purpose & Impact

• 🏗️ Greater Reliability: Release summaries and automation are now more dependable, even if GitHub APIs behave unexpectedly.
• 🧪 Stronger Testing: Broader test coverage means future updates are safer and less likely to introduce bugs.
• 📣 Improved Notifications: Up-to-date Slack integration ensures clearer communication about release status.
• 👩‍💻 Developer Confidence: Developers can trust that automation scripts will handle real-world scenarios and edge cases smoothly.
• 🚀 User Experience: End users benefit from more stable releases and fewer interruptions due to automation errors.

Overall, this update is focused on making the development and release process smoother, safer, and more transparent for everyone involved!

What's Changed

• Bump slackapi/slack-github-action from 2.0.0 to 2.1.0 by @dependabot[bot] in #471
• Bump slackapi/slack-github-action from 2.0.0 to 2.1.0 in /.github/workflows by @dependabot[bot] in #472
• Update test_update_markdown_codeblocks.py by @glenn-jocher in #473
• Robust summarize_release.py previous tag by @glenn-jocher in #475

Full Changelog: v0.0.85...v0.0.86

v0.0.85 - Test Python 3.8 (#470)

🌟 Summary

This release improves compatibility and reliability by expanding testing to Python 3.8 and fixing import issues for older Python versions. 🐍🔧

📊 Key Changes

• Added Python 3.8 to the continuous integration (CI) test matrix, ensuring tests run on both Python 3.8 and 3.13.
• Improved import handling for the tomllib library to prevent errors on Python versions below 3.11.
• Updated and refined tests to better support multiple Python versions.

🎯 Purpose & Impact

• Broadens support for users on legacy systems by ensuring the codebase works smoothly with Python 3.8.
• Reduces the risk of version-related errors, especially during publishing and deployment.
• Increases confidence for all users that the software is stable and reliable across a wider range of Python environments. 🚀
• Makes it easier for teams and organizations with diverse setups to adopt and use the latest features without compatibility concerns.

What's Changed

• Fix Python<3.11 errors by scoping tomlib import by @fcakyon in #469
• Test Python 3.8 by @glenn-jocher in #470

Full Changelog: v0.0.84...v0.0.85

v0.0.84 - New pub.dev version checks (#466)

🌟 Summary

Refactored and improved version-checking tools, adding support for Dart packages on pub.dev and making it easier to manage multi-language package publishing. 🚀

📊 Key Changes

• Moved version-checking logic into a new, dedicated version_utils.py module for better organization.
• Introduced check_pubdev_version to automatically check Dart package versions on pub.dev.
• Updated existing Python (PyPI) version-checking to use the new module.
• Improved code structure and imports for easier maintenance and future updates.

🎯 Purpose & Impact

• Cleaner, More Maintainable Code: Separating version-checking utilities makes the codebase easier to understand and extend.
• Broader Language Support: Now supports automated version checks for both Python and Dart packages, making the publishing process more versatile.
• Streamlined Publishing: Helps developers quickly determine when a new package version should be published, reducing manual checks and potential errors.
• Future-Proofing: Lays the groundwork for supporting additional languages or package managers in the future.

✨ This update is especially valuable for teams managing multiple package types, ensuring smoother and more reliable releases!

What's Changed

• New pub.dev version checks by @glenn-jocher in #466

Full Changelog: v0.0.83...v0.0.84

v0.0.83 - Improve handling of too-large PR diff (#465)

🌟 Summary

Enhanced error handling and workflow reliability in Ultralytics Actions, making GitHub integrations more robust and user-friendly. 🚀

📊 Key Changes

• Improved error messages for large or failed pull request (PR) diffs, clearly indicating issues when PRs exceed GitHub's 20,000-line limit or cannot be retrieved.
• Added explicit read-only permissions to workflows for improved security.
• Updated setup steps to gracefully handle empty working directories, preventing unnecessary errors.
• Reverted a previous change to Dart setup due to workflow failures, ensuring continued stability.

🎯 Purpose & Impact

• 🛠️ Makes troubleshooting easier by providing clear feedback when PR diffs are too large or unavailable, reducing confusion for developers.
• 🔒 Strengthens security by ensuring workflows only have the minimal permissions needed.
• 💡 Improves reliability of GitHub Actions, especially in diverse project setups or when directories are empty.
• 🚦 Ensures workflows remain stable and functional by reverting problematic changes quickly.

Overall, this release focuses on making the development process smoother, safer, and more transparent for all users working with Ultralytics Actions on GitHub.

What's Changed

• Potential fix for code scanning alert no. 6: Workflow does not contain permissions by @glenn-jocher in #461
• Update Dark install to use matrix strategy by @asabri97 in #462
• Revert "Update Dark install to use matrix strategy" by @glenn-jocher in #463
• Update action.yml for ignore-empty-workdir: true by @glenn-jocher in #464
• Improve handling of too-large PR diff by @glenn-jocher in #465

Full Changelog: v0.0.82...v0.0.83

v0.0.82 - Remove MATLAB from update_file_headers.py (#460)

🌟 Summary

A maintenance-focused update that streamlines file header management, strengthens workflow security, and improves testing reliability across the project. 🛠️🔒

📊 Key Changes

• 🧹 Removed special handling for MATLAB (.m) files in the file header update script, simplifying code maintenance.
• 📝 Added and improved automated tests for updating file headers, ensuring robust and consistent header management across different file types.
• 🔒 Enhanced GitHub Actions workflows by explicitly setting minimal permissions for CI and publishing jobs, boosting security.
• 🚀 Ensured the Dart SDK uses the stable channel in CI workflows for more reliable builds.
• 📦 Updated the package version to 0.0.82.

🎯 Purpose & Impact

• Simplifies Development: By removing unused MATLAB logic, the codebase is easier to maintain and less confusing for contributors.
• Boosts Security: Restricting workflow permissions reduces the risk of unauthorized changes and improves transparency for all contributors.
• Improves Reliability: Focused and comprehensive tests for file header updates help catch issues early and maintain consistent licensing and branding.
• Ensures Consistency: Using the stable Dart SDK in workflows prevents unexpected build failures and makes development smoother for everyone.
• Supports Contributors: These changes make it easier for both new and experienced developers to contribute confidently and efficiently. 🚀

Overall, this release focuses on making the project cleaner, safer, and more reliable for all users and contributors.

What's Changed

• Create test_headers.py by @glenn-jocher in #455
• Update and rename test_headers.py to test_file_headers.py by @glenn-jocher in #456
• Potential fix for code scanning alert no. 7: Workflow does not contain permissions by @glenn-jocher in #458
• Update action.yml for Dart sdk argument by @glenn-jocher in #459
• Update ci.yml with permissions by @glenn-jocher in #457
• Remove MATLAB from update_file_headers.py by @glenn-jocher in #460

Full Changelog: v0.0.81...v0.0.82

v0.0.81 - Exclude autogenerated files from header action (#454)

🌟 Summary

Improved code maintenance by refining which files are affected by automated header updates, leading to a cleaner and more efficient development process. 🧹🚀

📊 Key Changes

• Expanded the list of files and directories ignored by the file header update script, now covering more auto-generated and configuration files (like .eslintrc.js, swagger.yaml, .pb.py, BuildConfig.java).
• Organized the ignore list for better clarity and easier management.
• Minor cleanup in the retry action configuration by removing an unnecessary comment.
• Updated the package version to 0.0.81.

🎯 Purpose & Impact

• Prevents accidental or unnecessary changes to generated/configuration files, reducing clutter and potential errors for developers. 🛡️
• Speeds up and streamlines the file header update process, making it more reliable. ⚡
• Keeps the codebase tidy and easier to maintain, benefiting both contributors and users. 🧹
• No changes to user-facing features or model performance; these updates focus on behind-the-scenes improvements for smoother development.

What's Changed

• Update action.yml by @glenn-jocher in #453
• Exclude autogenerated files from header action by @glenn-jocher in #454

Full Changelog: v0.0.80...v0.0.81

v0.0.80 - Update update_file_headers.py (#452)

🌟 Summary

A small maintenance update improves file header management and prevents formatting issues in Vue files. 🛠️✨

📊 Key Changes

• Bumped the Ultralytics Actions package version from 0.0.79 to 0.0.80.
• Stopped automatic file header updates for .vue files to avoid conflicts with Prettier formatting.

🎯 Purpose & Impact

• Ensures Vue component files remain clean and properly formatted, reducing headaches for developers working with Prettier.
• Maintains clear versioning, signaling ongoing care and reliability in the Ultralytics Actions package.
• No changes to models or user-facing features—this update is focused on behind-the-scenes code quality and developer experience.

What's Changed

• Update update_file_headers.py by @glenn-jocher in #452

Full Changelog: v0.0.79...v0.0.80

v0.0.79 - Disable Vue due to 80-char wrap bug (#451)

🌟 Summary

Improved handling of file headers in Vue components to fix formatting issues, along with a version update. 🛠️✨

📊 Key Changes

• Updated the way file headers are added to .vue files, switching to HTML-style comments to prevent unwanted line wrapping.
• Increased the package version from 0.0.78 to 0.0.79.

🎯 Purpose & Impact

• Prevents formatting problems in Vue files caused by code tools like Prettier, making code easier to read and maintain.
• Keeps the project versioning current, signaling a small but helpful improvement for developers working with Vue components.
• Enhances the overall developer experience by ensuring consistent and correct file formatting.

What's Changed

• Disable Vue due to 80-char wrap bug by @glenn-jocher in #451

Full Changelog: v0.0.78...v0.0.79

v0.0.78 - Add Vue and Next.js file header formats (#450)

🌟 Summary

Expanded file header support to Vue, JSX, and TSX files, with smarter handling of Python docstrings for cleaner formatting. 🚀

📊 Key Changes

• Added automated file header updates for .vue, .jsx, and .tsx files, making the tool compatible with Vue, React, and Next.js projects.
• Improved logic to avoid inserting unnecessary blank lines before Python docstrings, ensuring tidier Python files.
• Updated version to 0.0.78.

🎯 Purpose & Impact

• Broadens compatibility for modern web development by supporting more frontend file types, helping teams maintain consistent file headers across diverse codebases.
• Reduces formatting issues in Python files, making code easier to read and maintain.
• Developers using Vue, React, or Next.js benefit from automated, standardized file headers, saving time and improving project professionalism. ✨

What's Changed

• Add Vue and Next.js file header formats by @glenn-jocher in #450

Full Changelog: v0.0.77...v0.0.78