@eppo/node-server-sdk - npm Package Compare versions

Comparing version 0.3.1 to 0.3.2

LICENSE

package.json

		{
		"name": "@eppo/node-server-sdk",
		"version": "0.3.1",
		"version": "0.3.2",
		"description": "Eppo node server SDK",
		@@ -26,3 +26,3 @@ "main": "dist/index.js",
		"author": "",
		"license": "UNLICENSED",
		"license": "Apache-2.0",
		"bugs": {
		@@ -29,0 +29,0 @@ "url": "https://github.com/Eppo-exp/node-server-sdk/issues"

README.md

		@@ -21,30 +21,1 @@ # Eppo Server-Side SDK for Node.js
		The client must be a singleton. The client instance stores assignment configurations in memory. To avoid inconsistent assignment results, the same client instance should be reused across requests. Invoke the `init` method once at application startup to generate the client.

		## Contributing

		### Pull Requests

		Create a new branch off of `main` and submit a PR. In the PR, update the `Unreleased` section of the changelog with a description of your change:

		```
		## Unreleased

		* Brief description of your change
		```

		Do not change the package version in the PR.

		### Release Process
		A release may include changes from multiple pull requests. Only the package maintainers have access to publish releases.

		1) Checkout the `main` branch and pull the latest changes

		2) Bump the package version: `npm version [major \| minor \| patch]`.

		- Follow [Semver guidelines](https://semver.org/) when choosing major \| minor \| patch

		3) Update CHANGELOG.md with the list of changes that have occurred since the last release. Commit the version bump and CHANGELOG updates to the main branch. Example:

		4) `npm login` - enter your credentials

		5) `npm publish`. (You can also do `npm publish --dryrun` to test)

Fixed alerts