ci(openfeature-node-server): fixing release please settings#1432
ci(openfeature-node-server): fixing release please settings#1432joker23 wants to merge 1 commit into
Conversation
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/browser size report |
3f344ec to
784f013
Compare
@launchdarkly/openfeature-node-server@1.3.0
@launchdarkly/openfeature-node-server@1.3.0|
closing this as I think we could just do the release. |
This PR will update the configuration for
packages/sdk/openfeature-node-serverin release please to:extra-filereference since the example is in a subdirectory of the workspacerelease-asto1.3.0to get this package ready to publish from this repoNote
Low Risk
Changes affect release automation and documentation only; no runtime SDK behavior is modified.
Overview
Updates release-please so the OpenFeature server packages can ship stable versions from this repo instead of staying on prerelease bumps.
For
packages/sdk/openfeature-node-server, it setsrelease-as:1.3.0, dropsbump-minor-pre-major, and fixes theextra-filesJSON path toexamples/getting-started/package.json(workspace-relative) so the getting-started example dependency version is updated on release. Forpackages/shared/openfeature-server-common, it replaces prerelease settings withrelease-as:1.0.0.Docs cleanup aligns with GA: experimental/pre-release CAUTION blocks are removed from both OpenFeature READMEs and NPM/CI badges are enabled. The
openfeature-node-serverCHANGELOG is reset to a bare header (prior version entries removed), consistent with a fresh release line.Reviewed by Cursor Bugbot for commit 784f013. Bugbot is set up for automated code reviews on this repo. Configure here.