Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Downgrade Semantic Kernel Version for Azure Function Compatibility #279

Merged
merged 1 commit into from
Jan 4, 2025

Conversation

Prasanjeet-Microsoft
Copy link
Contributor

Purpose

  • The purpose of downgrading the Semantic Kernel version in the requirements.txt file is to ensure compatibility and stability of the Azure Function app, as certain versions may introduce issues preventing proper execution. This action aims to resolve intermittent errors experienced when using the latest version of the Semantic Kernel.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • Verify if the function app starts without errors after the downgrade.
  • Confirm that all dependencies are properly installed post-downgrade.
  • Test the key functionality of the app to ensure it works as expected.
  • Monitor for any recurring errors that might indicate further issues with the downgrade.

@Copilot Copilot bot review requested due to automatic review settings January 3, 2025 18:51

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)
  • ClientAdvisor/AzureFunction/requirements.txt: Language not supported
@Prajwal-Microsoft Prajwal-Microsoft merged commit b3d9c23 into main Jan 4, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants