All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to a flavor of Semantic Versioning which includes Scopes and Epochs.
| Scope | Current Release | Commit Count |
|---|---|---|
| GitNet | 3.0.0 | 18 commits |
| SepochSemver | 0.5.0 | 3 commits |
| Markdown | 0.1.0 | None yet! |
- bump project file to 2026 by @shayanhabibi with #58efd
3.0.0 - (2026-02-01)
- dummy commit to force breaking change by @shayanhabibi with #5dff8
2.0.5 - (2026-02-01)
- Config CEs; previous operations would silently ignore errors now raise them. Use try-prefixed operations instead. (#8) by @cabboose with #cdf91
- fix typo in CEs by @shayanhabibi with #9fc54
2.0.4 - (2025-11-24)
- index write after staging by @shayanhabibi with #aa09c
2.0.3 - (2025-11-24)
- CrackedProject modification appropriately creates new elements prn by @shayanhabibi with #ad417
2.0.2 - (2025-11-24)
- ProjectFile does not require path combination by @shayanhabibi with #262a4
2.0.1 - (2025-11-24)
- CrackedProject stage helpers include the path to the project directory by @shayanhabibi with #6c984
2.0.0 - (2025-11-24)
1.2.0 - (2025-11-24)
-
slim the API down to only work for FSharp projects/solutions by @cabboose with #4e003
-
Revert "refactor!: Slim API and add proj helpers " (#6) by @cabboose with #d8cac
1.1.2 - (2025-11-22)
1.1.1 - (2025-11-22)
1.1.0 - (2025-11-21)
1.0.0 - (2025-11-21)
- GitNet runs and dry runs provide extra info in record form. Extra Run overloads. Merge #2 by @cabboose with #3d09d
0.1.2 - (2025-08-22)
0.1.1 - (2025-08-22)
0.5.0 - (2025-08-22)
No commits at this time.
Read more about this SemVer flavor
This flavor adds an optional marketable value called an EPOCH.
There is also an optional disambiguating SCOPE identifier for delineating tags for packages in a mono repo.
The motivation for this is to prevent resistance to utilising SemVer major bumps correctly, by allowing a separate marketable identifier which is easily compatible with the current SemVer spec.
An Epoch/Scope (Sepoch) is an OPTIONAL prefix to a typical SemVer.
- A Sepoch MUST BE bounded by
_underscores_. - The identifiers MUST BE ALPHABETICAL (A-Za-z) identifiers.
- The Epoch SHOULD BE upper case
- The Epoch MUST come before the Scope, if both are present.
- The Scope MUST additionally be bounded by
(parenthesis). - The Scope SHOULD BE capitalised/pascal cased.
- A Sepoch CAN BE separated from SemVer by a single white space where this is allowed (ie not allowed in git tags).
- Epoch DOES NOT influence precedence.
- Scope MUST uniquely identify a single components versioning.
- Different scopes CANNOT BE compared for precedence.
- A SemVer without a Scope CAN BE compared to a Scoped SemVer for compatibility. But caution is advised.
There is no enforcement for ordering EPOCHs in this spec, as it would be overly restrictive and yield little value since we can delineate and earlier EPOCH from a later EPOCH by the SemVers.
gitGraph
commit tag: "_ALPS_1.2.3"
branch develop
commit id: "add: ..."
commit
checkout main
cherry-pick id: "add: ..." tag: "_ALPS_2.1.3"
checkout develop
commit
commit
checkout main
merge develop tag: "_ALPS_3.4.5"
checkout develop
commit
commit
checkout main
merge develop tag: "_BRAVO_4.0.0" type: HIGHLIGHT
While there are breaking changes between versions 1 to 3, we expect that it is less than from 3 to 4. We expect the API surface would change more dramatically, or there is some other significant milestone improvement, in the change from version 3 epoch ALPS to version 4 epoch BRAVO.
_WILDLANDS(Core)_ 4.2.0
_WILDLANDS(Engine)_ 0.5.3
_DELTA(Core)_ 5.0.0
_DELTA(Engine)_ 0.5.3
Cannot be compared to Core versions. Both Engine versions are equal, we can identify that
the ecosystems marketed change does not change the Engine packages API