Repository navigation
Release 3.0.0 - #39
Merged
Merged
Conversation
npm's latest is 2.1.11, published 2026-08-14, and package.json still carried that same version -- so the 27 commits since then had nothing to publish from. The released tag contains only index.js, utils.js and zero-bounce.js: the Inbox Placement Tester, the SFTP bulk jobs, the Warmup client, listS3files and verify_plus have all been unreleased since August. Major rather than minor, because the error contract changed. In 2.1.11 notInitialized, parameterIsMissing and parameterIsInvalid called console.error and the method resolved to undefined; they now throw, so every public method rejects on a missing or invalid argument. A caller without a catch goes from a silent undefined to an unhandled rejection, which is not something to ship under a caret range. init rejecting a non-https apiBaseURL is breaking in the same way. Both are marked BREAKING in the changelog and summarised under the 3.0.0 heading. The changelog also gains the three published releases it never recorded: 2.1.9, 2.1.10 and 2.1.11, dated from their tags. 2.1.9 is dated 2026-06-18 to match its tag rather than the npm timestamp, which is the same moment in UTC and would otherwise sort it above 2.1.8. Verified at 3.0.0: webpack build, 143 jest tests, tsc --noEmit on the type consumer, and the dist smoke test. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Why a release
npm's latest is 2.1.11, published 2026-08-14, and
package.jsonstill carried that same version — so the 27 commits since then had nothing to publish from. Thev2.1.11tag contains onlyindex.js,utils.jsandzero-bounce.js.Unreleased until now:
listS3filesverify_plusWhy major, not minor
The error contract changed. In 2.1.11
notInitialized,parameterIsMissingandparameterIsInvalidcalledconsole.errorand the method resolved toundefined. They nowthrow, so every public method rejects on a missing or invalid argument — a caller without acatchgoes from a silentundefinedto an unhandled rejection.initrejecting a non-https://apiBaseURLbreaks in the same way.Shipping that under a caret range would upgrade consumers into it silently, so it is 3.0.0. Both lines are marked BREAKING in the changelog, with a summary under the 3.0.0 heading.
Also
The changelog gains the three published releases it never recorded: 2.1.9, 2.1.10 and 2.1.11, dated from their tags. 2.1.9 is dated 2026-06-18 to match its tag rather than the npm timestamp (the same moment in UTC), which would otherwise sort it above 2.1.8.
Verified at 3.0.0
npm run build— webpack, compiled successfullynpm test— 143 jest tests pass, plustsc --noEmiton the type consumernpm run test:smoke— dist exports check outPublishing stays manual:
publish.ymlisworkflow_dispatch, so merging and tagging will not push to npm.🤖 Generated with Claude Code