Release v6.6.69 - #913
Merged
Merged
Conversation
6.6.68 (PR #911) merged and tagged but never reached npm: the release workflow creates the GitHub release before running npm publish, so once tag v6.6.68 existed a re-run always failed at the release step and skipped the publish. Cutting a fresh version lets the publish job run. Content is identical to 6.6.68 — api-method-documentation 5.2.34 is already in the lockfile via #911; this is a version bump only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
spezzirriemiliano
approved these changes
Aug 26, 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
2 participants
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.
What
Release v6.6.69. This is a clean re-cut of 6.6.68 so the release actually reaches npm.
Why
6.6.68 (PR #911) was merged and tagged
v6.6.68, but it never published to npm. The release workflow ("Tests and publishing") runs the Github Release step beforenpm publish. Once the tag/releasev6.6.68existed, every re-run failed at the Github Release step withalready_existsand skipped the publish, so npm stayed on 6.6.66. A re-run can therefore never publish that version.Cutting a fresh version (6.6.69) sidesteps the stuck tag: the Github Release step succeeds for the new
v6.6.69, andnpm publishruns afterwards with the now-corrected CI credential.Changes
package.json: version6.6.68→6.6.69.package-lock.json: root /packages[""]version →6.6.69.No dependency changes. The 5.2.34
api-method-documentationfix (webhook URL-area alignment for OAS 3.1/3.2) is already in the lockfile via #911 — this is a version bump only, so 6.6.69 carries the exact same component set as 6.6.68.Refs