Repository navigation
chore: version packages - #355
Merged
Merged
Conversation
cuibonobo
force-pushed
the
changeset-release/main
branch
from
September 26, 2026 12:21
c8dd984 to
ad3a1df
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@haverstack/[email protected]
Minor Changes
@haverstack/core,@haverstack/wire-types.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/blob-adapter-disk,@haverstack/core,@haverstack/record-adapter-sqlite.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
#353
a431168Thanks @cuibonobo! - The./wirerequest parsers refuse input their endpoint does not define instead of ignoring it.parseQueryParams(),parseChangeParams()andparseJournalParams()throwStackBadRequestErrorfor an unknown query param, a repeat of a param that names one value, or a boolean param other thantrue/false.parseQueryBody()does the same for an unknown key at any depth, a non-object body, a non-booleanincludeDeleted/includeUnlistedor a non-stringcursor.createOptionsFromWireRecord()refuses a key no wire record carries. The rule is specified in docs/spec/wire-format.md § Unrecognized input, and four new error fixtures cover it.#356
4a3bc8eThanks @cuibonobo! -@haverstack/core/wireadds a parser for every remaining endpoint core specifies, so a server no longer keeps its own list of their param and field names:parseAuthChallengeBody(),parseAuthTokenBody(),parseEntityPatchBody(),parseTypeBody(),parseMigrationBody(),parseDeleteParams(),parseDownloadParams()andparseAssociationParams(). Each refuses an unknown name or a malformed boolean withStackBadRequestError, and a known body field of the wrong type withStackValidationError. Two error fixtures pin a non-booleanpurgeand an unknown key onPOST /auth/token.Stackrefuses an association, permission or grant-target element carrying a key its kind does not define, at every depth, withStackBadRequestError. This applies on every write that takes an element, on arelatedTofilter target, and ongrantType(),revokeType()andlistTypeGrants(). A_grantrecord'sgranteeis held to the same keys and refused withStackValidationError. A new error fixture pins an unknown key on a permission grantee.Patch Changes
@haverstack/[email protected]
Minor Changes
#353
a431168Thanks @cuibonobo! - The./wirerequest parsers refuse input their endpoint does not define instead of ignoring it.parseQueryParams(),parseChangeParams()andparseJournalParams()throwStackBadRequestErrorfor an unknown query param, a repeat of a param that names one value, or a boolean param other thantrue/false.parseQueryBody()does the same for an unknown key at any depth, a non-object body, a non-booleanincludeDeleted/includeUnlistedor a non-stringcursor.createOptionsFromWireRecord()refuses a key no wire record carries. The rule is specified in docs/spec/wire-format.md § Unrecognized input, and four new error fixtures cover it.#356
4a3bc8eThanks @cuibonobo! -@haverstack/core/wireadds a parser for every remaining endpoint core specifies, so a server no longer keeps its own list of their param and field names:parseAuthChallengeBody(),parseAuthTokenBody(),parseEntityPatchBody(),parseTypeBody(),parseMigrationBody(),parseDeleteParams(),parseDownloadParams()andparseAssociationParams(). Each refuses an unknown name or a malformed boolean withStackBadRequestError, and a known body field of the wrong type withStackValidationError. Two error fixtures pin a non-booleanpurgeand an unknown key onPOST /auth/token.Stackrefuses an association, permission or grant-target element carrying a key its kind does not define, at every depth, withStackBadRequestError. This applies on every write that takes an element, on arelatedTofilter target, and ongrantType(),revokeType()andlistTypeGrants(). A_grantrecord'sgranteeis held to the same keys and refused withStackValidationError. A new error fixture pins an unknown key on a permission grantee.@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]:@haverstack/[email protected]
Minor Changes
@haverstack/core.Patch Changes
a431168,4a3bc8e]: