Prepare release v1.24.0 (#955)

jaegertracing · May 30, 2022 · 217baa1 · 217baa1
1 parent e55b3a6
commit 217baa1
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -6,6 +6,13 @@
 
 ### Fixes
 
+## v1.24.0 (2022-06-01)
+
+### Enhancements
+
+- Support new user analytics events in the Monitor Tab ([@VladislavBryukhanov](https://github.com/VladislavBryukhanov) in [#943](https://github.com/jaegertracing/jaeger-ui/pull/943))
+- Use red on scatterplot for traces if any spans have an error=true tag ([@esnible](https://github.com/esnible) in [#951](https://github.com/jaegertracing/jaeger-ui/pull/951))
+
 ## v1.23.0 (2022-05-10)
 
 ### Enhancements

diff --git a/RELEASE.md b/RELEASE.md
@@ -8,7 +8,8 @@
    1. The PR title should match the format "Prepare release vX.Y.Z".
    1. CHANGELOG.md
       - Change the version of the current release from "Next (unreleased)" to "vX.Y.Z (Month D, YYYY)" where "vX.Y.Z" is the semver for this release.
-      - Make sure all relevant changes made since the last release are present and listed under the current release. [`scripts/get-changelog.js`](https://github.com/jaegertracing/jaeger-ui/blob/52780c897f21131472de9b81c96ebd63853917ee/scripts/get-changelog.js) might be useful.
+      - Make sure all relevant changes made since the last release are present and listed under the current release.
+        - Tip: Run `node scripts/get-changelog.js` script that prints a dozen most recent commits in the chagelog format.
       - If necessary, add a note detailing any impact to externally facing APIs.
    1. Update `packages/jaeger-ui/package.json#version` to refer to the version being released.
 1. Create a GitHub release.

diff --git a/packages/jaeger-ui/package.json b/packages/jaeger-ui/package.json
@@ -1,7 +1,7 @@
 {
   "private": true,
   "name": "jaeger-ui",
-  "version": "1.23.0",
+  "version": "1.24.0",
   "main": "src/index.js",
   "license": "Apache-2.0",
   "homepage": ".",