Skip to content

Commit a9b3c23

Browse files
authored
Merge pull request #27 from Monnify/dev
fix: sync version.json with the actual release version, fixing every …
2 parents 9d49e61 + 0de44cd commit a9b3c23

5 files changed

Lines changed: 12 additions & 2 deletions

File tree

.github/workflows/ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ jobs:
1515
- uses: actions/checkout@v7
1616
with:
1717
fetch-depth: 0 # full history - Nerdbank.GitVersioning needs it to compute the version
18+
fetch-tags: true # belt-and-braces so a tagged commit's tags are always visible to NBGV
1819

1920
- uses: actions/setup-dotnet@v5
2021
with:

.github/workflows/release.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ jobs:
2121
- uses: actions/checkout@v7
2222
with:
2323
fetch-depth: 0
24+
fetch-tags: true # belt-and-braces so a tagged commit's tags are always visible to NBGV
2425

2526
- uses: actions/setup-dotnet@v5
2627
with:

CHANGELOG.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,7 @@ own version is independent of Monnify's API versioning.
137137

138138
* envelope handling now tolerates endpoints (e.g. paycodes) that omit `requestSuccessful` from their response
139139
* a non-JSON error body (e.g. a proxy/gateway's own error page for a 502/504) on a failing HTTP status now throws `MonnifyApiException` with the real status code, instead of a misleading `MonnifyDeserializationException` — found via a real sandbox 502 while dogfooding the published package before v1
140+
* `version.json`'s Nerdbank.GitVersioning baseline had sat at `0.1-alpha` since the very first commit and was never kept in sync with the actual released version. NBGV only reads the version *number* from `version.json` itself - it never derives it from the git tag, even when it correctly detects a public-release tag - so every release published so far (`v0.1.0` through `v0.10.0`) actually shipped to NuGet.org as an unrelated `0.1.x-alpha` prerelease instead of its real tagged version. Fixed by bumping `version.json` to the real current version and wiring `release-please-config.json`'s `extra-files` to keep it in sync automatically on every future release, so this can't drift out of sync again
140141

141142
## [0.5.0](https://github.com/Monnify/monnify-dotnet-lib/compare/v0.4.0...v0.5.0) (2026-06-30)
142143

release-please-config.json

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,14 @@
44
"packages": {
55
".": {
66
"release-type": "simple",
7-
"changelog-path": "CHANGELOG.md"
7+
"changelog-path": "CHANGELOG.md",
8+
"extra-files": [
9+
{
10+
"type": "json",
11+
"path": "version.json",
12+
"jsonpath": "$.version"
13+
}
14+
]
815
}
916
}
1017
}

version.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"$schema": "https://raw.githubusercontent.com/dotnet/Nerdbank.GitVersioning/main/src/NerdBank.GitVersioning/version.schema.json",
3-
"version": "0.1-alpha",
3+
"version": "0.10.0",
44
"publicReleaseRefSpec": [
55
"^refs/tags/v\\d+\\.\\d+\\.\\d+$"
66
],

0 commit comments

Comments
 (0)