Skip to content

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

Closed
anilanar wants to merge 1 commit into
masterfrom
release-base-url-fix
Closed

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

Conversation

@anilanar
Copy link
Copy Markdown
Member

Summary

Re-opening PR #64 since the previous squash-merge didn't advance master (squash drops empty commits). This time please rebase-merge so the empty commit lands on master and release-please picks it up.

Otherwise the contents are unchanged: a single empty commit with a conventional fix(messenger-internal): message acting as a release marker for the base_url change that shipped in 4c1b7dc (#60) on 2026-05-13.

Expected outcome after rebase-merging

  • master gets a new commit (the empty 5cbeeeb with the conventional message)
  • release-please opens a Release PR with:
    • @userlike/messenger-internal 3.3.1 → 3.3.2
    • @userlike/messenger 2.0.1 → 2.0.2 (cascade via node-workspace plugin)

Test plan

  • CI passes
  • Use Rebase and merge (not Squash)
  • After merge, master HEAD changes (verify with git log or GH UI)
  • release-please opens a Release PR

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
Copy link
Copy Markdown
Member Author

Switching to a revert+reapply approach (PR coming). Two non-empty commits will let rebase-merge actually advance master.

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