Commit b1328e1
authored
chore(release): prepare v0.1.3 + auto-sync the bundle version pin in CI (#5)
The skill launcher (bin/sonar) reads SONAR_BUNDLE_VERSION from
plugin/skills/sonar-predictor/config.env to decide which
sonar-predictor-dist-<version>.zip to fetch from Maven Central on first
invocation. If that pin lags behind the release tag, every installed
plugin pulls the wrong bundle. Two changes here:
1. Bump SONAR_BUNDLE_VERSION 0.1.1 -> 0.1.3 in config.env so the v0.1.3
release artifact ships the correct pin.
2. Add a publish.yml step that sed-bumps that pin to match the derived
release version before the build, so future releases never hit this
trap again — the committed value becomes informational and the CI
step is the source of truth at deploy time.1 parent 523f634 commit b1328e1
2 files changed
Lines changed: 13 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
92 | 92 | | |
93 | 93 | | |
94 | 94 | | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
95 | 107 | | |
96 | 108 | | |
97 | 109 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
23 | | - | |
| 23 | + | |
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
| |||
0 commit comments