Skip to content

chore(release): release master#62

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
release-please--branches--master
Closed

chore(release): release master#62
github-actions[bot] wants to merge 1 commit into
masterfrom
release-please--branches--master

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 22, 2026

🤖 I have created a release beep boop

messenger: 2.1.0

2.1.0 (2026-05-22)

Features

  • add legacy api as v0 (935ace2)
  • add new api version v2 (6267723)
  • improve v2 type names (1fee6a6)
  • messenger: add browser compatible dist file (fda3814)
  • messenger: change browser dist file to umd format (6c8b27e)
  • rename ActionResult to Result and swap generic args (08218f9)

Bug Fixes

  • fix version mismatch in createMessenger types (f343cb1)
  • messenger: add browser dist file to published list of files (ea76dd4)
  • messenger: remove 'browser' main field (9fa457f)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @userlike/messenger-internal bumped to 4.0.0
messenger-internal: 4.0.0

4.0.0 (2026-05-22)

⚠ BREAKING CHANGES

  • messenger-internal: widget_key and config fields are removed from WidgetLoader.

Features

  • add consumeToken to v1 api (a2ad6c4)
  • add contact info to exposed um state (68921c3)
  • add contact verification (e989a71)
  • add experimental __unstableOpenConversation to v1 api (71af30e)
  • add experimental setRegistration and setProactive actions (bbdf3e7)
  • add legacy api as v0 (935ace2)
  • add new api version v2 (6267723)
  • add new contact form fields (f0897cd)
  • add nonce for csp to mount options (70e2796)
  • add openConversationId to mount options (07e7d45)
  • add optional nonce to LegacyOptions (46e5466)
  • add support for an optional credentials param to v1 api mount (9a62ce4)
  • allow reporting of original errors for script load events (f05ff4b)
  • extend mount api to return reason when no messenger mounts (e628076)
  • improve v2 type names (1fee6a6)
  • increase iframe accessibility (1d861d5)
  • internal: add loadWidgetConfig & loadAssetsManifest (ebe1ba4)
  • introduce experimental ui config option (47b9ed7)
  • introduce minimize (e803a17)
  • introduce show/hide, separate from mount/unmount (1d976a1)
  • rename ActionResult to Result and swap generic args (08218f9)

Bug Fixes

  • add nonce to WidgetLoaderSettings too (0da6b2e)
  • fix accidental take-over of document title (ba1829d)
  • fix return type of v2 mount (da5e725)
  • fix script loader iframe's style (e2a14e1)
  • fix script loader iframe's style (9995de9)
  • improve error handling of widget loading (c1870f8)
  • internal: drop process.env usage (38858b7), closes #12
  • make iframe style csp compliant (e97a239)
  • make VersionStatus a non-const enum (c03c1fc)
  • move nonce type into v0 CreateMessengerSettings (a5cdec8)
  • reduce the chance of multiple messengers conflicting with each other (e7bc350)
  • remove mention of AuthParams (8fde53c)

Code Refactoring

  • drop config from WidgetLoaderSettings (bc32432)
  • impl asset loading from umm manifest (9c9cfbd)
  • messenger-internal: remove unnecessary fields from WidgetLoader interface (c61471d)

This PR was generated with Release Please. See documentation.

@anilanar
Copy link
Copy Markdown
Member

anilanar commented May 22, 2026

Closing — the bumps in this PR (2.1.0, 4.0.0) come from release-please scanning the entire git history since the dawn of the repo rather than just since the last release. Root cause: the tag format release-please generates ('messenger@v2.0.1') doesn't match the existing repo tags ('@userlike/messenger@2.0.1'), so it can't find any prior release and falls back to 'scan everything.' Fixing the tag config now; release-please will reopen a fresh (and empty) Release PR after the fix merges.

@anilanar anilanar closed this May 22, 2026
@anilanar anilanar mentioned this pull request May 22, 2026
Merged
3 tasks
anilanar added a commit that referenced this pull request May 22, 2026
@anilanar
fix(repo): align release-please tag format with existing tags
e5bbe5a 
release-please was generating tags as 'messenger@v2.0.1' (component =
directory name, v-prefix on version), but the existing repo tags are
'@userlike/messenger@2.0.1' (component = full scoped name, no v).
The mismatch meant release-please couldn't find any prior tag for
either package and fell back to scanning all of git history - it
then proposed to 're-release' ancient feat: and BREAKING CHANGE:
commits, bumping messenger-internal to 4.0.0 over an old widget_key
removal and messenger to 2.1.0 over old feat:s. See closed PR #62.

Fix:
- component: '@userlike/messenger' (and same for -internal) overrides
  the directory-name default.
- include-v-in-tag: false drops the v-prefix.

After this lands, release-please will compute tags as
'@userlike/messenger@<version>' which matches the existing tags
exactly, find the right starting points, and scan only commits since
2.0.1 / 3.3.1. Since none of those are conventional-commit
feat:/fix:/BREAKING, no release PR should open.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

process.env is required

1 participant

@anilanar