docs(changelog): record PR #14 hardening + trigger first canary#15
Merged
Conversation
bntvllnt
force-pushed
the
docs/changelog-pr14
branch
from
75c3980 to
f54ae17
Compare
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
1 participant
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.
Documents the #14 hardening work (request body cap, loopback Host guard, unsupported-param rejection, server timeouts, faux-provider tests) in the CHANGELOG Unreleased section.
This is also the first canary trigger now that
vars.ENABLE_CANARY=trueand npm trusted publishing are configured. Merging this to main should auto-publishpi-gateway@0.1.0-canary.<sha>to npm with thecanarydist-tag via the Publish workflow's canary job (OIDC trusted publishing + provenance).