Skip to content

Commit ccb0c98

Browse files
committed
docs: remove unused section of RELEASING.md
1 parent f289d26 commit ccb0c98

File tree

2 files changed

+1
-4
lines changed

2 files changed

+1
-4
lines changed

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10-
## [0.4.4]
10+
## [0.4.4] - 2023-02-16
1111

1212
### Added
1313

RELEASING.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,6 @@ To release a new version of **stactools** or a [stactools-package](https://githu
3232
Include a "Release summary" section which includes the contents of your section of the CHANGELOG.
3333
9. Once approved, merge the branch.
3434
10. Create an **annotated** tag at the new **main** HEAD named `vX.X.X`, e.g. `v0.3.0`.
35-
- The contents of the tag should be the CHANGELOG contents for your version release.
36-
Be sure to remove any leading `###`, they'll be considered comments in the tag contents.
37-
See previous annotated tags for examples of formatting.
3835
11. Push your tag.
3936
This will fire off a special [release Github action](.github/workflows/release.yml) that will push your package to PyPI.
4037
12. Create a new release for your tag in the [Github releases](https://github.com/stac-utils/stactools/releases).

0 commit comments

Comments
 (0)