umd 0.1.1

Universal Markdown - A post-Markdown superset with Bootstrap 5 integration and extensible syntax
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

# Release Process

This document defines maintainers' release workflow for `umd`.

## Versioning policy

This project follows Semantic Versioning.

- Patch: bug fixes, no breaking API changes
- Minor: backward-compatible features
- Major: breaking API/behavior changes

## Release checklist

1. Update `Cargo.toml` version.
2. Update `CHANGELOG.md` for the target version.
3. Run validation:

```bash
cargo build --verbose
cargo test --verbose
```

4. Verify package contents:

```bash
cargo package --list
```

5. Publish according to `PUBLISHING.md`.
6. Create git tag: `vX.Y.Z`.
7. Create GitHub Release with summary from `CHANGELOG.md`.
8. Update or add a versioned release note file (e.g. `RELEASE_NOTES_v0.1.0.md`) and paste it into the GitHub Release body.

## Release notes format

Use concise, user-facing bullets grouped by:

- Added
- Changed
- Fixed
- Removed

## Rollback policy

Published crates cannot be deleted. If a release is incorrect:

1. Publish a corrected patch version.
2. Document the issue and fix in `CHANGELOG.md`.
3. Communicate recommended upgrade path in GitHub Release notes.