Skip to content

chore(main): release 1.6.0 - #61

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore(main): release 1.6.0#61
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.6.0 (2026-08-31)

Features

  • Add configurable event and flag poll intervals to the bridge (#60) (7aebb5b)
  • Retry the event push to LaunchDarkly once before giving up (#69) (76f68d1)
  • Support more than one LaunchDarkly project and environment per Salesforce org (#64) (941055a)
  • Support the OAuth client credentials flow in the bridge (#65) (4536966)

Bug Fixes

  • Check the error from constructing the event poll request (#67) (7e9a41d)
  • Check the token response body read error where the body is load-bearing (#68) (74f3036)
  • Finish with HTTP responses so connections can be reused (#62) (9477007)
  • Make a zero cache TTL disable caching instead of disabling flag data (#66) (07dec93)
  • Report the real error when the flag push request cannot be built (#71) (860b311)
  • Retry a Salesforce request once after refreshing the token (#70) (08a8836)

This PR was generated with Release Please. See documentation.


Note

Overview
Cuts release 1.6.0 by bumping the Release Please manifest, the bridge SDK_VERSION constant (and User-Agent), and adding the 1.6.0 section to CHANGELOG.md.

This diff does not introduce new runtime logic—the only code change is the version string. The changelog records work already merged since 1.5.1: configurable event/flag poll intervals, OAuth client credentials, multi-project/environment scoping via LD_SCOPE_KEY, event-push and Salesforce token retries, HTTP connection reuse, cache TTL behavior, and several error-handling fixes in the bridge.

Reviewed by Cursor Bugbot for commit 9edeb96. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
github-actions Bot requested a review from a team as a code owner July 31, 2026 18:35
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 3aa0f22 to 3a0ef33 Compare July 31, 2026 20:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from 6f6e590 to 2f871de Compare August 27, 2026 16:08
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 5 times, most recently from 2a17c66 to 91fe156 Compare August 31, 2026 18:35
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 91fe156 to 9edeb96 Compare August 31, 2026 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants