Skip to content

Conversation

deansheather
Copy link
Member

Previously, if you had a new license that would start before the current one fully expired, you would get a warning. Now, the license validity periods are merged together, and a warning is only generated based on the end of the current contiguous period of license coverage.

If you have used AI to produce some or all of this PR, please ensure you have read our AI Contribution guidelines before submitting.

Closes #19498

Previously, if you had a new license that would start before the current
one fully expired, you would get a warning. Now, the license validity
periods are merged together, and a warning is only generated based on
the end of the current contiguous period of license coverage.
@deansheather deansheather requested a review from Emyrk August 28, 2025 04:20
@matifali matifali added the cherry-pick/v2.26 Needs to be cherry-picked to the 2.26 release branch label Aug 28, 2025
Copy link
Member

@Emyrk Emyrk left a comment

Choose a reason for hiding this comment

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

This makes no changes to the entitlements, just the license expiration warning 👍

@deansheather deansheather enabled auto-merge (squash) August 29, 2025 13:44
@deansheather deansheather merged commit 605dad8 into main Aug 29, 2025
31 checks passed
@deansheather deansheather deleted the dean/suppress-license-expiry branch August 29, 2025 13:53
@github-actions github-actions bot locked and limited conversation to collaborators Aug 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cherry-pick/v2.26 Needs to be cherry-picked to the 2.26 release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upcoming license expiry generates license warnings, even if a newer license exists
3 participants