Skip to content

Commit 93ccd22

Browse files
committed
Release: prepare v1.0.0
1 parent b39431a commit 93ccd22

3 files changed

Lines changed: 9 additions & 8 deletions

File tree

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ All notable changes to this project will be documented in this file.
1010

1111
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).
1212

13-
## [Unreleased] (1.0.0)
13+
## [1.0.0] - 2024-04-21
1414
### Added
1515
- New types:
1616
- `LocalPath` for paths that may be either absolute or relative, and stored in a normalized way;

Directory.Build.props

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ SPDX-License-Identifier: MIT
66

77
<Project>
88
<PropertyGroup Label="Packaging">
9-
<Version>0.0.0</Version>
9+
<Version>1.0.0</Version>
1010
<PackageLicenseExpression>MIT</PackageLicenseExpression>
1111
<Copyright>© 2024 Friedrich von Never</Copyright>
1212
<PackageReadmeFile>README.md</PackageReadmeFile>

MAINTAINING.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,13 @@ Maintainer Guide
99

1010
Publish a New Version
1111
---------------------
12-
1. Update the copyright year in the `Directory.Build.props` file, if required.
13-
2. Prepare a corresponding entry in the `CHANGELOG.md` file (usually by renaming the "Unreleased" section).
14-
3. Set `<Version>` in the `Directory.Build.props` file.
15-
4. Merge the aforementioned changes via a pull request.
16-
5. Check if the NuGet key is still valid (see the **Rotate NuGet Publishing Key** section if it isn't).
17-
6. Push a tag in form of `v<VERSION>`, e.g. `v0.0.0`. GitHub Actions will do the rest (push a NuGet package).
12+
1. Update the project's status in the `README.md` file, if required.
13+
2. Update the copyright statement in the `Directory.Build.props` file, if required.
14+
3. Prepare a corresponding entry in the `CHANGELOG.md` file (usually by renaming the "Unreleased" section).
15+
4. Set `<Version>` in the `Directory.Build.props` file.
16+
5. Merge the aforementioned changes via a pull request.
17+
6. Check if the NuGet key is still valid (see the **Rotate NuGet Publishing Key** section if it isn't).
18+
7. Push a tag in form of `v<VERSION>`, e.g. `v0.0.0`. GitHub Actions will do the rest (push a NuGet package).
1819

1920
Rotate NuGet Publishing Key
2021
---------------------------

0 commit comments

Comments
 (0)