rss 2.1.2

Library for serializing the RSS web content syndication format
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

# Releasing

This project follows [Semantic Versioning](https://semver.org/):

- Use a patch release for backward-compatible bug fixes.
- Use a minor release for backward-compatible public API additions. Treat an
  increased minimum supported Rust version as a minor release.
- Use a major release for incompatible public API changes.

## Prepare the release

1. Start a `release/X.Y.Z` branch from the latest `master`.
2. Update the package version with `cargo set-version X.Y.Z`.
3. Add a dated `X.Y.Z` section below `Unreleased` in `CHANGELOG.md`. Include all
   user-visible changes since the previous release and link their pull requests.
4. Commit only the version and release documentation changes with the subject
   `chore: release rss X.Y.Z`.
5. Run the release checks from a clean worktree:

   ```console
   cargo test --all-features --no-fail-fast --all
   cargo publish --dry-run
   ```

6. Open a pull request and wait for its CI checks to pass. Keep it as a draft
   until the intended release contents and version are settled.

## Publish the release

1. Merge the release pull request.
2. Check out the updated `master` and confirm that `Cargo.toml` and
   `CHANGELOG.md` contain the intended version.
3. Run `cargo publish --dry-run` once more from the clean release commit, then
   publish it with `cargo publish`.
4. Create the GitHub release with automatically generated notes. Pass the full
   release commit SHA so the new tag cannot accidentally point to a later
   `master` commit:

   ```console
   gh release create X.Y.Z \
     --repo rust-syndication/rss \
     --target RELEASE_COMMIT_SHA \
     --title X.Y.Z \
     --generate-notes \
     --fail-on-no-commits
   ```

   If the tag does not exist, this command creates it at `RELEASE_COMMIT_SHA`.
5. Confirm that the version is available on crates.io. Run
   `gh release view X.Y.Z --repo rust-syndication/rss` and confirm that the
   GitHub release and tag point to the published commit.

Published crate versions cannot be overwritten, so resolve any version,
packaging, or CI problem before running `cargo publish`.