Commit 5a8aac4
authored
fix(ci): use simple release-type with extra-files for Gradle project (#145)
Switch Release Please configuration to use the 'simple' release type
with 'extra-files' instead of 'version-file' approach. This is the
recommended configuration for Gradle projects since Release Please
doesn't have native Gradle support.
Changes:
- Use 'extra-files' to update gradle.properties instead of version-file
- Add version marker (# x-release-please-version) to gradle.properties
- Remove version-file and version-file-prefix configuration
This fixes the "Empty change set" error by avoiding snapshot bumps
that the 'java' release type was attempting. The 'simple' release type
will now correctly create release PRs (0.41.0 → 0.42.0) based on
conventional commits without trying to create intermediate snapshot
versions.
Tested locally and confirmed it creates proper release PRs with
changelog and version updates.
Test locally with:
```
release-please release-pr --repo-url=forcedotcom/datacloud-jdbc \
--config-file=release-please-config.json \
--manifest-file=.release-please-manifest.json \
--target-branch=<branch-name> \
--token=\"\$GITHUB_TOKEN\" \
--dry-run"
```1 parent 8518b23 commit 5a8aac4
2 files changed
+5
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | | - | |
6 | | - | |
| 4 | + | |
7 | 5 | | |
8 | | - | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
0 commit comments