release: v0.4.8 (#433)

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.8] - 2023-06-01
+
 ### Added
 
 - `--no-resolve-links` to the copy command ([#430](https://github.com/stac-utils/stactools/pull/430))
@@ -387,7 +389,8 @@ See [#9](https://github.com/stac-utils/stactools/pull/9)
 - `stac.cli.command.layout` for modifying the layout of STACs
 - `stac.browse` for launching a local instance of stac-browser using docker.
 
-[Unreleased]: <https://github.com/stac-utils/stactools/compare/v0.4.7..main>
+[Unreleased]: <https://github.com/stac-utils/stactools/compare/v0.4.8..main>
+[0.4.8]: <https://github.com/stac-utils/stactools/compare/v0.4.7..v0.4.8>
 [0.4.7]: <https://github.com/stac-utils/stactools/compare/v0.4.6..v0.4.7>
 [0.4.6]: <https://github.com/stac-utils/stactools/compare/v0.4.5..v0.4.6>
 [0.4.5]: <https://github.com/stac-utils/stactools/compare/v0.4.4..v0.4.5>

RELEASING.md

@@ -29,7 +29,6 @@ To release a new version of **stactools** or a [stactools-package](https://githu
    4. Update the `[Unreleased]` link at the bottom of the page to start at your new release.
    5. Audit your new section of the CHANGELOG to ensure all relevant changes are captured.
 8. Open a pull request for your branch.
-   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`.
 11. Push your tag.
@@ -42,6 +41,6 @@ To release a new version of **stactools** or a [stactools-package](https://githu
 
 Yes, **stactools-packages** should follow their own release schedule, as their stability tied to **stactools** itself.
 
-### Is there a roadmap for stac-utils 1.0?
+### Is there a roadmap for stactools 1.0?
 
 Not at this time.

src/stactools/core/__init__.py

@@ -24,4 +24,4 @@
     "move_all_assets",
     "use_fsspec",
 ]
-__version__ = "0.4.7"
+__version__ = "0.4.8"