Skip to content

fix(messenger-internal): pass base_url through to run() (#60)#64

Merged
anilanar merged 1 commit into
masterfrom
release-base-url-fix
May 22, 2026
Merged

fix(messenger-internal): pass base_url through to run() (#60)#64
anilanar merged 1 commit into
masterfrom
release-base-url-fix

Conversation

@anilanar
Copy link
Copy Markdown
Member

Summary

Releasing the base_url fix that landed in 4c1b7dc (#60) on 2026-05-13. The original commit used the non-conventional internal: prefix, so release-please ignored it.

This PR is a single empty commit with a proper fix(messenger-internal): message — it carries no code change (the actual code is already on master), it's just a release marker so release-please picks the fix up for the next release.

Expected outcome after merge

  • release-please opens a Release PR proposing:
    • @userlike/messenger-internal 3.3.1 → 3.3.2 (patch, from this fix:)
    • @userlike/messenger 2.0.1 → 2.0.2 (cascade patch via node-workspace plugin)
  • Merging that Release PR creates two GH releases.
  • publish.yml stages both on npmjs.com.
  • You approve messenger-internal@3.3.2 first, then messenger@2.0.2.

Test plan

  • CI passes
  • After merge, release-please opens a Release PR with the right bumps

The code change shipped in 4c1b7dc (#60) on 2026-05-13 but its commit
message used the non-conventional 'internal:' prefix, which
release-please doesn't recognize as a releasing type. As a result the
fix has been sitting on master unreleased.

This empty commit gives the fix a conventional-commit marker so
release-please picks it up and includes it in the next release (a
patch bump on messenger-internal, plus a cascade patch bump on
messenger via the node-workspace plugin).

The original change makes baseUrl available so the messenger bundle
knows which origin served its loader. Backwards compatible: baseUrl
is optional. Existing umm bundles ignore the new field; bundles that
read it fall back to their env-baked URL when older messenger-internal
omits it.
@anilanar anilanar merged commit e5bbe5a into master May 22, 2026
1 check passed
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