0.1.15-staging.1

Changelog 0.1.15

Update this file continuously during development for version 0.1.15.

Highlights

• Add notable changes for this version.

0.1.15-staging.0

Changelog 0.1.15

Update this file continuously during development for version 0.1.15.

Highlights

• Add notable changes for this version.

0.1.14-staging.2

Changelog 0.1.14

Update this file continuously during development for version 0.1.14.

Highlights

• Add notable changes for this version.

0.1.14-staging.1

Changelog 0.1.14

Update this file continuously during development for version 0.1.14.

Highlights

• Add notable changes for this version.

0.1.14-staging.0

Changelog 0.1.14

Update this file continuously during development for version 0.1.14.

Highlights

• Add notable changes for this version.

0.1.13-staging.0

Changelog 0.1.13

Update this file continuously during development for version 0.1.13.

Highlights

• Add notable changes for this version.

0.1.12-staging.0

Changelog 0.1.12

Update this file continuously during development for version 0.1.12.

Highlights

• Add notable changes for this version.

0.1.11-staging.0

Changelog 0.1.11

Update this file continuously during development for version 0.1.11.

Highlights

• Add notable changes for this version.

0.1.10-staging.0

Changelog (upcoming)

Edit on develop only. This file powers GitHub release notes and archive files when a publish runs from alpha (prerelease tags X.Y.Z-staging.N + float :staging), beta (-beta.N + :beta), or main (RTM X.Y.Z + :prod). See PUBLISH.

List most important user-facing or ops changes first. Keep the list concise, not a git log.

The block between the markers is reset (via a PR to develop) after a successful publish. Add static notes above the marker block; only the marked block is auto-reset.

0.1.9-staging.2

Changelog (upcoming)

Edit on develop only. This file powers GitHub release notes and archive files when a publish runs from alpha (prerelease tags X.Y.Z-staging.N + float :staging), beta (-beta.N + :beta), or main (RTM X.Y.Z + :prod). See PUBLISH.

List most important user-facing or ops changes first. Keep the list concise, not a git log.

The block between the markers is reset (via a PR to develop) after a successful publish. Add static notes above the marker block; only the marked block is auto-reset.