v0.60.1

• Added CI fix for hatch dependency (#4433). A temporary fix has been implemented to address a dependency issue with hatch, specifically related to a problem with the Click library, as tracked in the Click project. To ensure compatibility and prevent errors in the testing process, which relies on hatch, the installation of hatch now includes a version constraint for the Click library, ensuring that a version less than 8.3.0 is installed. This adjustment provides a workaround for a known issue, allowing the testing framework to proceed without disruptions, and ensuring that the project's testing dependency on hatch remains functional until a more permanent solution is available.
• Enhanced Assessment Export (#4432). The export functionality has been enhanced to handle large assessment exports by implementing a zip compression strategy, preventing export failures due to file size limitations. This is achieved by creating a zip archive containing the Excel file, which is generated using a ZipFile object and an ExcelWriter object writing to a BytesIO buffer. Error handling has been added to handle missing queries, allowing the export process to continue without interruption. Various functions, including those responsible for downloading and exporting assessment results, have been updated to work with the new zip file format, including changes to file names and download links. Additionally, test cases have been modified to verify the successful export of assessment results as zip files, ensuring that the new compression strategy is functioning correctly and transparently handling large exports.
• Split assess_workflows task into its new Workflow (#4395). The workflow assessment functionality has been decoupled from the main Assessment workflow and introduced as a standalone task, providing users with greater control over when and how workflow assessment is executed. This task, which retrieves jobs to analyze their notebooks and files for migration problems, can be triggered manually using the new run-assess-workflows command, allowing users to optionally run the assessment for a collection of workspaces. The Assessment workflow has been modified to remove the workflow assessment task, reducing its complexity, and a new Workflow assessment section has been added to the documentation to describe the new task's functionality and usage. The introduction of this standalone task enables users to assess workflows that ran within the last 30 days, with the option to analyze all workflows, and provides more flexibility and control over the assessment process, which was previously bundled within the Assessment workflow and potentially prolonged the overall run time.

Contributors: @pritishpai, @andresgarciaf