Release v6.6.68 - #911
Merged
Merged
Conversation
Fast-follow over 6.6.67 to pull in the webhook URL-area alignment fix (api-method-documentation 5.2.34): the OAS 3.1/3.2 webhook event name now lines up with the method pill instead of carrying a stray top margin. Bumps the package version to 6.6.68 and re-resolves the deduped api-method-documentation lock entry to 5.2.34 (CSS-only change; its dependency set is unchanged from 5.2.33). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alexpmule
marked this pull request as ready for review
August 26, 2026 17:52
spezzirriemiliano
approved these changes
Aug 26, 2026
Merged
pull Bot
pushed a commit
to xjc90s/api-console
that referenced
this pull request
Aug 26, 2026
6.6.68 (PR mulesoft#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 mulesoft#911; this is a version bump only. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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
Fast-follow release v6.6.68 over 6.6.67. Adopts
@api-components/api-method-documentation@5.2.34.Why
5.2.34 carries the webhook URL-area alignment fix: for OAS 3.1/3.2 webhook operations the
event name now lines up with the method pill instead of being pushed down by a stray
margin-top. The fix is CSS-only (.url-value > .url-server-value:first-child { margin-top: 0 }),merged upstream in advanced-rest-client/api-method-documentation#102 and published to npm as 5.2.34.
6.6.67 shipped before that component was published, so this is a small follow-up to pull it in.
Changes
package.json: version6.6.67→6.6.68.package-lock.json: root/packages[""]version →6.6.68; re-resolve the dedupedapi-method-documentationentry to5.2.34(resolved+integrityupdated). Its dependencyset is unchanged from 5.2.33 (CSS-only change). No
package.jsondependency ranges changed —the component is transitive under
api-documentation@6.1.9and^5.2.30already satisfies 5.2.34.npm publish note (resolved)
The 6.6.67 master-merge run failed at the publish step with:
Root cause was the CI npm credential (
NODE_AUTH_TOKEN), not the repo config — on an existingpublic package, an authenticated
PUTreturning 404 is how npm rejects an expired/invalid token.The token has since been rotated, so publishing is unblocked. Merging this PR publishes 6.6.68
(which carries the 6.6.67 content plus the 5.2.34 fix) in a single pass; npm simply skips the
never-published 6.6.67.
Refs