fledge 0.9.1

Dev-lifecycle CLI — scaffolding, tasks, lanes, plugins, and more.
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
55
56
57
58
59
60
61
62
63
64

# Changelog

fledge generates changelogs from your git tags and conventional commits.

## Usage

```bash
fledge changelog                 # recent releases
fledge changelog --unreleased    # changes since last tag
fledge changelog --tag v0.7.0    # specific release
fledge changelog --limit 5       # last 5 releases
fledge changelog --json          # machine-readable
```

## Commit Format

fledge follows [Conventional Commits](https://www.conventionalcommits.org/). The format is:

```
<type>[optional scope]: <description>
```

**Types and how they appear in the changelog:**

| Type | Section |
|------|---------|
| `feat` | Features |
| `fix` | Bug Fixes |
| `docs` | Documentation |
| `chore` | Maintenance |
| `refactor` | Refactoring |
| `perf` | Performance |
| `test` | Tests |
| `ci` | CI/CD |

Breaking changes use `!` after the type (`feat!: ...`) or a `BREAKING CHANGE:` footer. They get their own section at the top.

**Examples:**

```
feat: add dark mode toggle
fix(auth): handle expired tokens
feat!: remove legacy config format
chore: bump dependencies
```

## Versioning

fledge reads git tags that follow semver (`v1.2.3`). Each tag becomes a changelog section. Commits without a tag end up in the `--unreleased` section.

## Config

No config required. fledge reads your git history directly.

Optional `fledge.toml` settings:

```toml
[changelog]
types = ["feat", "fix", "perf"]   # only include these types
```

## Full Changelog

See [CHANGELOG.md](https://github.com/CorvidLabs/fledge/blob/main/CHANGELOG.md) for the complete release history.