From 87e7b6927af7500200017b5da61107c0da803769 Mon Sep 17 00:00:00 2001 From: Michael Marchetti Date: Tue, 31 May 2022 14:01:12 -0400 Subject: [PATCH 1/2] Fix changelog heading for 1.8.0 --- CHANGELOG.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 47e4b237..0faf2386 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,13 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -## Unreleased +## [1.8.1] - 2022-05-31 + +### Changed + +Corrected changelog heading. + +## [1.8.0] - 2022-05-31 ### Added From 84598a9d101dd8492136cd4f87a47c3773d1917e Mon Sep 17 00:00:00 2001 From: Michael Marchetti Date: Tue, 31 May 2022 14:01:28 -0400 Subject: [PATCH 2/2] note in contribute doc re changelog headings --- CONTRIBUTING.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cb583593..f6277b0c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,6 +60,9 @@ All version and release management is done via [annotated git tags](https://git- repo metadata used by the [`setuptools_scm`](https://github.com/pypa/setuptools_scm) package to generate the version string provided as `rsconnect:VERSION` and output by `rsconnect version`. +Before releasing, replace the `Unreleased` heading in the changelog +with the version number and date. + To create a new release, create and push an annotated git tag: ```bash