[CORE-4832] Update TLS documentation to reflect TLS 1.3 support#141
Merged
Conversation
asmith-pd
approved these changes
Jul 21, 2026
joaovgsantos
approved these changes
Jul 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Updates the REST API Overview documentation to reflect TLS 1.3 support across all PagerDuty ingress endpoints.
Changes
docs/REST-API/01-Overview.md: Updated the TLS section to note that both TLS 1.2 and 1.3 are now supported, with a recommendation to use 1.3 where available.Why
As part of CORE-4832, TLS 1.3 is being rolled out across all ingress endpoints. This doc update ensures developers are aware of the expanded protocol support. TLS 1.2 remains fully supported for backwards compatibility — no client-side changes are required.