0.45 release notes #55
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
changelogs/api-management-service.md
Outdated
| ### New features, improvements, and changes | ||
|
|
||
| - HTTP/2 connections are now drained and gracefully terminated before node restarts | ||
| - We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy |
Contributor
There was a problem hiding this comment.
The correct link is https://learn.microsoft.com/azure/api-management/validate-azure-ad-token-policy
changelogs/api-management-service.md
Outdated
| - We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors | ||
| - Load balancer feature ... | ||
| - Expressions are now work as expected for in the `<audience/>` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy | ||
| - We fixed a bug that caused XML entities to be erroneously unescaped in the policy documents |
Contributor
There was a problem hiding this comment.
- Not XML entities, but text values of XML elements.
- Decoded, not unescaped.
- Only within liquid templates.
changelogs/api-management-service.md
Outdated
| - HTTP/2 connections are now drained and gracefully terminated before node restarts | ||
| - We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-azure-ad-token-policy) policy | ||
| - [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. | ||
| - We've imprioved promt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy |
Contributor
There was a problem hiding this comment.
Typos on improved and prompt
simonkurtz-MSFT
suggested changes
Jun 26, 2024
changelogs/api-management-service.md
Outdated
|
|
||
| - We fixed an issue which caused GraphQL resolver runtime errors when primitive type fileds had null value | ||
| - We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors | ||
| - Expressions are now work as expected for in the `<audience/>` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy |
Contributor
There was a problem hiding this comment.
Change to Expressions now work as expected in the <audience/> elements ...
ferantoMSFT
reviewed
Jun 26, 2024
| - [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. | ||
| - We've improved prompt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy | ||
| - We've made [request tracing](https://learn.microsoft.com/azure/api-management/api-management-howto-api-inspector) more secure and it's now available in both Classic and V2 tiers | ||
| - Now customers can use Azure portal to [migrate](https://learn.microsoft.com/azure/api-management/migrate-stv1-to-stv2-vnet?#trigger-migration-of-a-network-injected-api-management-instance) their stv1 service instances to stv2 |
There was a problem hiding this comment.
@vladvino please let's change "their stv1 service instances to stv2" to "their VNet injected stv1 service instances to stv2"... emphasis on VNet Injected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.