Releases: ultralytics/actions
v0.0.22 - Update to v0.0.22 with SHA report (#298)
🌟 Summary
Release v0.0.22 of ultralytics/actions
includes notable updates to its default OpenAI model and improved GitHub Actions traceability, alongside a version increment. 🚀
📊 Key Changes
- Version Increment: The version has been updated from 0.0.21 to 0.0.22.
- OpenAI Model Update: Default model updated from "gpt-4o" to "gpt-4o-2024-11-20" for enhanced processing capability.
- GitHub Actions Enhancement: Added
base SHA
to action outputs for better workflow context and traceability.
🎯 Purpose & Impact
- Version Update: Indicates a fresh release that may contain improvements and bug fixes. Users should reference detailed release notes to appreciate all modifications.
- Enhanced AI Model: The newer OpenAI model promises better performance and compatibility, automatically providing non-customized users with these advancements.
- Improved Traceability: Including the
base SHA
improves debugging and auditing in workflows by providing detailed commit information, simplifying processes for developers.
What's Changed
- Update to
gpt-4o-2024-11-20
by @glenn-jocher in #296 - Add base SHA to printout by @glenn-jocher in #297
- Update to v0.0.22 with SHA report by @glenn-jocher in #298
Full Changelog: v0.0.21...v0.0.22
v0.0.21 - Prettier 3.4 update (#294)
🌟 Summary
Release v0.0.21 introduces improvements in code formatting and handling, primarily focusing on more robust markdown processing with updated Prettier support. ⚙️✨
📊 Key Changes
- 🚀 Markdown Processing: Now applies formatting only if the
./docs
directory exists, to avoid potential errors. - 🔄 Code Revision: Commented out Python scripts related to MkDocs reference tweaks to simplify maintenance.
- 📈 Version Bump: Software version updated from
0.0.20
to0.0.21
indicating minor enhancements and fixes.
🎯 Purpose & Impact
- 🛡️ Improved Robustness: By checking for the existence of the
./docs
directory before applying formatting, the process becomes more error-resistant, ensuring smoother project setup. - 💡 Maintenance Simplification: Temporarily disabling certain scripts makes maintenance more manageable without affecting key functionalities.
- 📊 Enhanced Stability: The increment in version underscores enhancements in markdown handling, which can lead to cleaner, more consistent documentation and improved user experience.
What's Changed
- Ultralytics Refactor https://ultralytics.com/actions by @pderrenger in #292
- Update action.yml by @glenn-jocher in #293
- Prettier 3.4 update by @glenn-jocher in #294
Full Changelog: v0.0.20...v0.0.21
v0.0.20 - Update __init__.py to v0.0.20 (#291)
🌟 Summary
The ultralytics/actions
package has been updated to version 0.0.20! This update primarily includes improvements to code formatting processes and a new version tag. 🚀
📊 Key Changes
- Version Update: The version number in the
__init__.py
file has been incremented from0.0.19
to0.0.20
. - Prettier Configuration Enhanced: The Prettier tool, used for code formatting, now covers a broader range of file types including
js
,vue
,ts
, and more. - Improved Exclusions: Specific files like
model.json
are now excluded from automated formatting to protect their specific formatting needs.
🎯 Purpose & Impact
- Versioning Clarity: The update to version 0.0.20 helps users easily track changes and ensures they have the most current version for optimal functionality and any potential bug fixes.
- Unified Code Styling: By extending Prettier's reach, developers benefit from a consistent code style, minimizing manual corrections and improving collaboration efficiency across various programming languages. 🧑💻
- Targeted Formatting: The exclusion of certain files allows for more precise control over what gets formatted, maintaining necessary customizations and preventing unintended changes. 🎯
- Contributor Ease: With automatic formatting standards in place, contributors can focus more on functionality and logic rather than style, enhancing productivity. ⚡️
What's Changed
- Update action.yml by @glenn-jocher in #289
- Update action.yml by @glenn-jocher in #290
- Update init.py to v0.0.20 by @glenn-jocher in #291
Full Changelog: v0.0.19...v0.0.20
v0.0.19 - Slack v2 API usage (#288)
🌟 Summary
The v0.0.19
release primarily enhances the Slack integration by upgrading to Slack API version 2, along with several other improvements in retry logic, package installation processes, and minor bug fixes.
📊 Key Changes
- Slack API Update: Upgraded to
slackapi/[email protected]
, utilizing theincoming-webhook
for notifications. - Retry Enhancements: Refined the retry logic to better manage errors and retries, providing clearer diagnostics and structured outputs.
- Package Management: Improved setup for package installation on macOS, avoiding unnecessary commands and aligning with best practices.
- Code Optimizations: Cleaned up and optimized the code for improved performance and readability.
🎯 Purpose & Impact
- Notification Improvements: The updated Slack integration can offer enhanced notification features, ensuring timely communication of action results. 📝
- Simplified Configuration: The move to
incoming-webhook
potentially simplifies Slack setup, improving reliability and reducing setup complexity. 🔧 - Efficient Troubleshooting: Enhanced retry error messaging aids in quicker issue resolution, by offering a more transparent retry process and error reporting. 🛠️
- Cross-Platform Compatibility: Adjustments in package handling on macOS prevent environmental issues, ensuring a smoother user experience across different operating systems. 🍏
- Streamlined Processes: Code refinements and optimizations lead to faster execution and easier maintenance, benefiting developers and users alike. 🚀
What's Changed
- Fix PyPI downloads links by @pderrenger in #278
- Fix retry count and add docstring by @glenn-jocher in #279
- Update action.yaml by @glenn-jocher in #280
- Revert "Update action.yaml" by @glenn-jocher in #282
- Update action.yaml by @glenn-jocher in #283
- Use uv for package installation by @glenn-jocher in #284
- Update action.yml by @glenn-jocher in #285
- Update action.yml by @glenn-jocher in #286
- Update action.yml by @glenn-jocher in #287
- Slack v2 API usage by @glenn-jocher in #288
Full Changelog: v0.0.18...v0.0.19
v0.0.18 - Update environment in publish.yml (#276)
🌟 Summary
The latest release, v0.0.18, primarily focuses on enhancing the GitHub Actions workflow for better release management and tracking, with updates to environment configurations and notification formats.
📊 Key Changes
- Environment Configuration: Introduces an environment parameter in the GitHub Actions workflow for improved documentation and tracking of releases through the GitHub Deployments tab.
- Slack Notification Enhancements: Tweaks to the format of Slack notifications to improve readability by switching quotation marks to backticks around repository variables.
- Configurable Git Commit Information: Adds new optional inputs for GitHub username and email, allowing user customization during commit operations.
- Exclusion of
.lock
Files: Updates the spell-check process to skip.lock
files, which often contain immutable package information. - Bump in Lycheeverse Version: Updates the lychee-action version, which helps in checking for broken links, to benefit from new features and fixes.
🎯 Purpose & Impact
- Enhanced Release Management: By specifying environments, developers can now track multiple versions more clearly, boosting clarity and organization within the release process. 📦
- Improved Communication: The tweaks in notification formatting make it easier for teams to understand automated messages, enhancing collaboration. 📬
- Customization and Flexibility: Allowing users to define their commit details encourages a more personalized and flexible workflow, suited to various team needs. 🔄
- Efficiency in Spell-checking: Ignoring
.lock
files in spell checks cuts down on false positives, streamlining the development process and allowing developers to focus on meaningful corrections. 🚀 - Robust Link Checking: Utilizing the latest version of the link checker ensures better detection and reporting of link issues, enhancing the overall robustness of the documentation and repository content. 🔗
What's Changed
- Update publish.yml by @glenn-jocher in #272
- Update action.yml by @glenn-jocher in #273
- Ignore lockfiles for spelling by @glenn-jocher in #274
- Bump lycheeverse/lychee-action from 1.10.0 to 2.0.2 by @dependabot[bot] in #275
- Update environment in publish.yml by @glenn-jocher in #276
Full Changelog: v0.0.17...v0.0.18
v0.0.17 - Prettier ignore npm and poetry lock files (#271)
🌟 Summary
The v0.0.17 release focuses on improving code formatting management, enhancing server efficiency, and ensuring compatibility with future Python versions.
📊 Key Changes
- Updated Prettier configuration to ignore 'lock' files during formatting.
- Introduced a new GitHub Action for disk space cleanup on servers.
- Simplified file naming for disk cleanup action for better clarity.
- Updated retry action with clearer input variable names.
- Added support for Python 3.13 compatibility.
🎯 Purpose & Impact
- Formatting Efficiency: By excluding lock files from Prettier formatting, this update prevents unnecessary formatting on configuration files, improving development workflow clarity. 🚫🔒
- Server Optimization: The disk space cleanup action helps free up server storage, enhancing build process efficiency and making more resources available for essential activities. 🚀
- Simplified Maintenance: Renaming actions and inputs to be more intuitive ensures the repository is developer-friendly and easy to navigate. 🧩
- Future-Ready: Adding support for Python 3.13 prepares the project for seamless transitions to newer Python versions, future-proofing the system. 🐍✨
These updates collectively aim to streamline development processes, enhance operational efficiency, and ensure long-term compatibility and clarity in the project.
What's Changed
- Disk Space Cleanup Action by @glenn-jocher in #267
- Rename Cleanup disk action by @glenn-jocher in #268
- Stop attempting to remove Android cache by @glenn-jocher in #269
- Update retry/action.yaml by @glenn-jocher in #270
- Prettier ignore npm and poetry lock files by @glenn-jocher in #271
Full Changelog: v0.0.16...v0.0.17
v0.0.16 - Fix duplicate PR summary (#266)
🌟 Summary
Version 0.0.16 brings improvements to the process of summarizing pull requests, ensuring more consistent and clear communication. 🚀
📊 Key Changes
- Updated the version from
0.0.15
to0.0.16
. - Modified the
summarize_pr.py
script to prepend a constantSUMMARY_START
to every PR summary.
🎯 Purpose & Impact
- Version Upgrade: The increment in version indicates enhancements have been made, signaling ongoing improvements and maintenance of the project. 🔧
- Enhanced PR Summaries: By standardizing the start of each summary, this change aims to improve the consistency and clarity of information, making it easier for users to understand updates. 📝
- User Benefits: Users will benefit from more uniform and easy-to-digest PR summaries, without any alteration to the core functionalities they rely on. This update primarily enhances the user experience in terms of information presentation. 📈
What's Changed
- Fix duplicate PR summary by @glenn-jocher in #266
Full Changelog: v0.0.15...v0.0.16
v0.0.15 - Print Ultralytics Actions version (#265)
🌟 Summary
The v0.0.15 release primarily updates the Ultralytics Actions to include version printing, enhancing transparency and traceability for users and developers.
📊 Key Changes
- Version Display: The release now includes functionality to print the current version of Ultralytics Actions whenever information is displayed. This is visible in the information header, making it easier to identify the version being used.
🎯 Purpose & Impact
- Improved Clarity: By displaying the version number, users can more easily verify which version is running, aiding in troubleshooting and development.
- Enhanced Communication: Maintainers and collaborators can quickly ensure they have the latest version installed and communicate more effectively when discussing issues or updates.
What's Changed
- Print Ultralytics Actions version by @glenn-jocher in #265
Full Changelog: v0.0.14...v0.0.15
v0.0.14 - Update summarize_pr.py (#264)
🌟 Summary
The v0.0.14 release enhances the GitHub Actions used in the Ultralytics repository, focusing on improving the management and updating of pull request (PR) summaries.
📊 Key Changes
- Version Bump: The software version is updated from 0.0.13 to 0.0.14. 📈
- PR Summary Header Introduction: A new header
## 🛠️ PR Summary
is introduced to help auto-detect existing summaries. - Logic Enhancement: Implemented new logic to either replace existing summaries or append new ones if no summary is found.
🎯 Purpose & Impact
- Improved Documentation Clarity: By standardizing the header for PR summaries, users can more easily identify and interact with these summaries. 🛠️
- Streamlined Workflow: The enhanced logic makes the PR management process more reliable, reducing human error and improving maintenance efficiency. 🔧
- User and Developer Experience: Enhances clarity and consistency in communication within the development process, making it easier for both users and contributors to follow updates. 🗂️
What's Changed
- Update summarize_pr.py by @glenn-jocher in #264
Full Changelog: v0.0.13...v0.0.14
v0.0.13 - Fix duplicate PR summary (#263)
🌟 Summary
Version 0.0.13 enhances the process for generating and updating pull request (PR) summaries, focusing on improving functionality, clarity, and reliability.
📊 Key Changes
- Incremented the version from 0.0.12 to 0.0.13.
- Introduced the
time
module to handle retries more effectively. - Simplified the logic in the
generate_pr_summary
function to streamline its return process. - Improved
update_pr_description
to better handle cases with no existing description, incorporating retry mechanisms and clear notifications.
🎯 Purpose & Impact
- 📚 Enhanced Clarity: The streamlined code makes it easier for developers to understand and maintain PR summaries, minimizing confusion.
- 🚀 Increased Reliability: Adding retry logic and alerts when updating PR descriptions ensures a smoother and more consistent update process, reducing errors.
- 🎯 Simplified Maintenance: The refactor allows for easier future modifications and debugging, aiding both new and seasoned developers in code management.
What's Changed
- Fix duplicate PR summary by @glenn-jocher in #263
Full Changelog: v0.0.12...v0.0.13