docs: add changelog entry for 2026.4.0–2026.5.0#355
Open
mintlify[bot] wants to merge 2 commits into
Open
Conversation
liyasthomas
approved these changes
Jun 5, 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
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
Adds a combined changelog entry covering releases 2026.4.0, 2026.4.1, and 2026.5.0, plus the GHSA-c3fq-x5hm-p482 published-docs security fix.
Changes
id_tokensupport.$randomUUIDRFC 4122 compliance, Postman import resilience, mock server domain URL, team subfolder write-access, GQL history schema, personal workspace docs publishing, dependency CVE patches.Context
Triggered by hoppscotch/hoppscotch#6386 (GHSA-c3fq-x5hm-p482). The last changelog entry covered 2026.3.0/2026.3.1; this entry catches up the published changelog with everything shipped since then.