release mockopampserver 0.3.0 (#858)

Author: trentm

RELEASING.md

@@ -26,7 +26,7 @@ Assuming "x.y.z" is the release verison:
 2. Create a PR with these changes:
     - Bump the "version" in "packages/opentelemetry-node/package.json".
     - Run `npm install` in "packages/opentelemetry-node/" to update "packages/opentelemetry-node/package-lock.json".
-    - Update "packages/opentelemetry-node/CHANGELOG.md" as necessary.
+    - Update release notes in "docs/release-notes/*" as necessary.
     - Name the PR something like "release @elastic/opentelemetry-node@x.y.z".
 
 3. Get the PR approved and merged.

packages/mockopampserver/CHANGELOG.md

@@ -1,13 +1,14 @@
 # @elastic/mockopampserver Changelog
 
-## Unreleased
+## v0.3.0
 
 - Add a `POST /api/agentConfigMap` API endpoint that is only supported if
   `testMode` is true. This is not an OpAMP endpoint. It exists to support
   dev/test changing the agent config on the fly. Example usage with curl:
+
         curl -i http://127.0.0.1:4320/api/agentConfigMap -F 'elastic={"logging_level":"debug"}'
 
-- Drop `--json-remote-config-file` CLI option. in favour of more capable
+- Drop `--json-remote-config-file` CLI option in favour of more capable
   `-F` option. See example usage in `npm run example:*` scripts in package.json.
 
 ## v0.2.0

packages/mockopampserver/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@elastic/mockopampserver",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "type": "commonjs",
   "description": "A mock OpAMP server, useful for dev and testing",
   "publishConfig": {