Skip to content

5.2.35 - #103

Closed
alexpmule wants to merge 1 commit into
masterfrom
release/5.2.35
Closed

5.2.35#103
alexpmule wants to merge 1 commit into
masterfrom
release/5.2.35

Conversation

@alexpmule

Copy link
Copy Markdown
Contributor

What

Version bump to 5.2.35 to publish the webhook URL-area alignment fix.

Why

The alignment fix already merged to master in #102, and master's package.json is at 5.2.34, but npm was never updated — the latest published version is still 5.2.33. The "Tests and publishing" workflow did not run on the squash-merge push to master (that merge produced no push-triggered run), so 5.2.34 was never published.

This PR bumps the version so that merging it produces a fresh push to master, which triggers the publish workflow and ships the fix to npm. Since master is already at 5.2.34, the bump targets 5.2.35.

Changes

  • package.json + package-lock.json: 5.2.345.2.35 (via npm version patch).

No source changes — the alignment fix itself is already on master from #102.

Refs

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@alexpmule

Copy link
Copy Markdown
Contributor Author

Closing as redundant. 5.2.34 (which already contains this fix, merged in #102) published successfully to npm once the delayed 'Tests and publishing' push run finally executed on master — the earlier missing run was a GitHub event-processing delay, not a config issue. No separate 5.2.35 bump is needed.

@alexpmule alexpmule closed this Aug 26, 2026
@alexpmule
alexpmule deleted the release/5.2.35 branch August 26, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant