AI Prompts for Resolving Package Version Conflicts

Please provide the exact version number of [PACKAGE_NAME] that is currently installed in my project. Additionally, include any relevant information about the installation date and any dependencies that may be affected by this version. If there are any known issues or updates related to this version, please summarize those as well.

Please check the required version of [PACKAGE_NAME] as specified in my package.json or requirements file. Provide the exact version number listed and any additional information about compatibility or dependencies related to this package. If there are any discrepancies or potential issues with the version, please highlight those as well. Format your response clearly, indicating the version and any relevant notes.

Please compare the installed version of [PACKAGE_NAME] with the required version specified in the project dependencies. Identify if there is a version mismatch and provide a summary of the differences, including the installed version, the required version, and any potential implications of using the incorrect version. If a mismatch is found, suggest steps to resolve the issue, including how to update the package to the correct version. Format your response in a clear, structured manner.

Provide the complete dependency tree for [PACKAGE_NAME] in a structured format. Include details such as the version numbers of each dependency, any conflicting dependencies that may arise, and the reasons for these conflicts. Additionally, summarize how these dependencies interact with each other and suggest potential solutions to resolve any conflicts identified. Ensure the output is clear and easy to understand for further analysis.

Check if the installed version of [PACKAGE_NAME] is deprecated or has known issues. Analyze the version history and release notes to identify any critical problems associated with this version. Summarize the findings, including the reasons for deprecation, any reported bugs or vulnerabilities, and recommendations for upgrading to a stable version. Present this information in a clear format that highlights the key points for easy reference.

Please provide the exact command to update the package [PACKAGE_NAME] to the required version. Include any necessary flags or options that should be used in the command. Additionally, explain any potential issues that might arise during the update process and how to resolve them. If applicable, mention how to verify that the update was successful after executing the command.

Please provide detailed instructions on how to modify the dependency constraints for [PACKAGE_NAME] in my configuration file to avoid conflicts. Include specific examples of what the modified constraints should look like, and explain the rationale behind each change. Additionally, outline any potential issues that could arise from these modifications and how to address them. The response should be structured in a clear format that I can easily follow.

Identify the conflicting packages that are causing the version conflict with [PACKAGE_NAME]. Analyze the dependencies and versions in your project to determine which packages are incompatible. Provide a detailed list of the packages that should be removed, along with a brief explanation of why each package is causing the conflict. Additionally, suggest any alternative packages or versions that could be used to resolve the issue while maintaining the functionality of the project.

Please provide a detailed explanation of the package manager options available for forcing the installation of a specific version of [PACKAGE_NAME]. Include examples for popular package managers such as npm, pip, and gem, outlining the commands needed to specify the version explicitly. Additionally, discuss any potential issues that may arise from forcing a version and how to resolve them. Format your response in a clear, step-by-step guide that I can follow.

Please provide a list of alternative packages or versions that can be used instead of [PACKAGE_NAME] to resolve the conflict. Include details about each alternative, such as its compatibility with my current setup, any major differences in functionality, and potential advantages or disadvantages compared to [PACKAGE_NAME]. Additionally, suggest any steps I should take to implement these alternatives in my project, including any necessary adjustments to my code or configuration files.

Please confirm that [PACKAGE_NAME] has been updated to the correct version. Provide the current version number and any relevant details about the update process. Additionally, check for any potential issues or warnings related to this version and summarize them. If applicable, include instructions on how to resolve any issues that may arise from the update.

Please conduct a thorough dependency check for the project that includes [PACKAGE_NAME]. Identify any potential conflicts or issues that may arise from the current package versions in use. Provide a detailed report that outlines any discrepancies, suggests resolutions for conflicts, and lists any packages that may need to be updated or removed to ensure compatibility. Additionally, include recommendations for best practices in managing dependencies moving forward.

Please conduct a thorough test of the application to verify that it functions correctly after resolving the package version issue. Outline the specific areas of the application that should be tested, including any critical features or functionalities that may have been affected. Document any errors or unexpected behavior encountered during testing, and provide suggestions for further improvements or fixes if necessary. Additionally, summarize the overall performance of the application post-resolution, highlighting any enhancements or persistent issues.

After fixing the package version, please check for any new errors or warnings that may have appeared. List each error or warning with a brief description of what it means and possible solutions to resolve them. Additionally, indicate whether these issues are critical or can be addressed later. If there are no new errors or warnings, please confirm that as well.

Please validate the dependency tree for my project to ensure that all package versions are compatible and up-to-date. Provide a detailed report that includes any outdated packages, potential conflicts between dependencies, and suggestions for resolving these issues. Additionally, list the current versions of each package and indicate which ones need to be updated. Format the output in a clear, organized manner, so I can easily identify the necessary changes.

Please create a CLAUDE.md rule that specifies how to lock specific package versions in order to prevent future conflicts during installations. The rule should include the syntax for defining the version constraints, examples of how to apply it to different packages, and any best practices for maintaining these locks. Additionally, explain the implications of version locking on project dependencies and how it can help in ensuring stability across environments. Format the response in a clear, structured manner suitable for inclusion in a project documentation.

Create a comprehensive checklist for safely updating dependencies in a software project. The checklist should include the following steps: first, review the current package versions and identify any outdated dependencies; second, check the release notes or changelogs for each dependency to verify compatibility with your project; third, run tests to ensure that the updates do not break existing functionality; fourth, document any changes made during the update process; and finally, communicate with the team about the updates and any potential impacts. Format this checklist in a clear, numbered list for easy reference.

Please provide a detailed explanation of the version constraints for [PACKAGE_NAME] in the configuration file. Include the reasons for selecting each version, any potential compatibility issues that may arise with other packages, and how these constraints help prevent future installation problems. Additionally, format the comments clearly so that they are easy to understand for someone reviewing the file later. Aim for a comprehensive overview that covers all relevant aspects of the versioning strategy.

Please suggest a detailed naming convention for branches and commits specifically related to dependency updates in a software project. The convention should include guidelines on how to format branch names, such as using prefixes to indicate the type of update (e.g., feature, fix, chore), and how to structure commit messages to clearly communicate the changes made. Additionally, provide examples of naming conventions that can help maintain clarity and consistency across the project, ensuring that team members can easily understand the purpose of each branch or commit.

Create a script that automatically checks for version conflicts in project dependencies before allowing any changes to be merged into the main branch. The script should analyze the current version of each package listed in the project's configuration file and compare it against the versions specified in the incoming changes. If any conflicts are detected, the script should output a clear error message detailing the conflicting packages and their versions. Additionally, include instructions on how to resolve these conflicts, and ensure the script is written in [PROGRAMMING LANGUAGE] with comments for clarity.