From 418b9f3a6a43a458776927cef2bc0e8d158a071b Mon Sep 17 00:00:00 2001 From: Sergej Herbert Date: Tue, 26 Dec 2023 12:09:15 +0100 Subject: [PATCH] docs: update changelog and development release steps --- CHANGELOG.md | 10 ++++++++++ DEVELOPMENT.md | 9 ++++----- 2 files changed, 14 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d720dc5..1d3ecdf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,16 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com) and follows semantic Versioning. +## [Unreleased] + +Thank you to the collaborators on this release: + +- [@eeddaann](https://github.com/eeddaann) + +### Added + +- added support for Grafana annotations + ## [3.3.3] - 2023-07-21 ### Changed diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 9e3cfea..2aaf3cd 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -70,9 +70,8 @@ On MacOs you can use the preinstalled "screen sharing" application as a VNC view After step 3 Github Actions should take over and create a new release. Steps 4 and 5 are for publishing the release to Grafana repository. -1. Update the Changelog and the package.json -2. Tag the commit with a Semver tag, e.g. v2.2.3-rc.1 -3. Push the changes including the tag -4. Get the md5 hash of the release from the Github Action or from the release page (text file) -5. Within the Grafana Cloud account a request for a plugin update can be started: +1. Make sure a section in the Changelog exists with `## [Unreleased]` +2. Push the changes and merge to the default branch +3. Get the md5 hash of the release from the Github Action or from the release page (text file) +4. Within the Grafana Cloud account a request for a plugin update can be started: