docs: remove unused section of RELEASING.md

stac-utils · Feb 16, 2023 · ccb0c98 · ccb0c98
1 parent f289d26
commit ccb0c98
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.4.4]
+## [0.4.4] - 2023-02-16
 
 ### Added
 

diff --git a/RELEASING.md b/RELEASING.md
@@ -32,9 +32,6 @@ To release a new version of **stactools** or a [stactools-package](https://githu
    Include a "Release summary" section which includes the contents of your section of the CHANGELOG.
 9. Once approved, merge the branch.
 10. Create an **annotated** tag at the new **main** HEAD named `vX.X.X`, e.g. `v0.3.0`.
-    - The contents of the tag should be the CHANGELOG contents for your version release.
-      Be sure to remove any leading `###`, they'll be considered comments in the tag contents.
-      See previous annotated tags for examples of formatting.
 11. Push your tag.
     This will fire off a special [release Github action](.github/workflows/release.yml) that will push your package to PyPI.
 12. Create a new release for your tag in the [Github releases](https://github.com/stac-utils/stactools/releases).