Conversation
Vadman97
changed the title
Vadman97
changed the title
kinyoklion
approved these changes
Apr 1, 2026
mayberryzane
approved these changes
Apr 1, 2026
Merged
Vadman97
pushed a commit
that referenced
this pull request
Apr 1, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>observability: 1.1.2</summary> ## [1.1.2](observability-1.1.1...observability-1.1.2) (2026-04-01) ### Bug Fixes * OIDC publishing with npm ([#454](#454)) ([ab4221b](ab4221b)) </details> <details><summary>session-replay: 1.1.2</summary> ## [1.1.2](session-replay-1.1.1...session-replay-1.1.2) (2026-04-01) ### Bug Fixes * OIDC publishing with npm ([#454](#454)) ([ab4221b](ab4221b)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk: this PR only updates release metadata (versions and changelogs) with no functional code changes. > > **Overview** > Cuts a patch release for `@launchdarkly/observability` and `@launchdarkly/session-replay`, bumping both from `1.1.1` to `1.1.2` in the release manifest and each package’s `package.json`. > > Updates both `CHANGELOG.md` files to document the `1.1.2` bug fix: *OIDC publishing with npm*. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit f91f726. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
abelonogov-ld
added a commit
that referenced
this pull request
Apr 3, 2026
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
3 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.
Summary
npm publishdoes not correctly packageyarnmonorepo workspace dependencies.Update the publishing to use
yarn packto ensure the package is bundled correctly.Fixes #448
How did you test this change?
publishing from branch
Are there any deployment considerations?
Note
Medium Risk
Changes the npm publishing workflow to publish packed tarballs instead of workspace directories, which can affect what gets shipped to npm and release reliability. Low code complexity, but failures would impact package consumers/releases.
Overview
Fixes npm publishing for Yarn workspaces by switching
scripts/publish-npm.shfromnpm publish <workspace dir>toyarn pack+npm publish <tarball>, ensuringworkspace:*dependencies are resolved to real versions and cleaning up the temp tarball on success/failure.Also tweaks package descriptions in
@launchdarkly/observabilityand@launchdarkly/session-replay(wording/grammar only).Written by Cursor Bugbot for commit 2604d9b. This will update automatically on new commits. Configure here.