Version Packages - #51
Merged
Merged
Conversation
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.
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
@ingram-tech/nk-dev@0.15.0
Minor Changes
69c92b6: vitest 5. The shared config and setup file are unchanged, and no test in
nextkit needed an edit, but a site's suite may notice the new defaults:
tests unless you opt out with
clearMocks: false);expect(...).resolves/rejectsnow fails the test;vi.mockoutside a file's top level throws;sequentialis gone (tests are sequential unlessconcurrent);toHaveTextContentis strict; usetoMatchTextContentforsubstring matching;
.vitest/(add it to.gitignore);-tuses>as the suite separator;enginesalready required.Patch Changes
/internal/forms/<name>via nk-forms'createFormsHandler,never under
/api. The/apivs/internalrule is now about contract, notcaller:
/apiis what someone could build on;/internalis everything the appowns, including its own browser-called forms, which are bot-gated rather than
worker-secret-gated.
this repo.
@ingram-tech/nk-forms@0.4.0
Minor Changes
createFormsHandler+defineForm: one{ GET, POST }route for everypublic form on the site, mounted at
/internal/forms/[form]. The registry keybecomes the URL, the log label and the rate-limit namespace, so adding a form is
adding an entry instead of copying a route file. The site's limiter is a
callback receiving
{ request, form, limit, windowMs }(per-form budgetsoverride a handler-wide default of 5 per 10 minutes); nk-forms still owns no
store.
formEndpoint(name)/FORMS_BASE_PATH(root and/react) build theclient URL. Forms move out of
/api: it is the public API contract, and a formPOST is not part of it.
handleFormSubmissionandmintFormTokenremain for astandalone route.
Patch Changes
@ingram-tech/nk-auth@0.16.1
Patch Changes
(nk-billing). No API change.
@ingram-tech/nk-billing@0.3.8
Patch Changes
(nk-billing). No API change.