Skip to content

Commit fef269a

Browse files
authored
chore: limit commit-search-depth to 10 for server-side package (#274)
It appears release-please is looking far back in history when determining the release version of the server package. During this search, it also appears to be running into a SSE commit that didn't use conventional commit formatting. Now, it's unclear if this is connected - but it might be making release-please think that an SSE bump is required. My theory is that by limiting to 10 commits (not sure how low this could be - 0?) we can eliminate the issue. This should be ok since we know for a fact no conventional commits have happened to SSE client that would affect the server.
1 parent 01c528a commit fef269a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

release-please-config.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,8 @@
2020
],
2121
"prerelease": true,
2222
"bump-minor-pre-major": true,
23-
"release-as": "0.1.0"
23+
"release-as": "0.1.0",
24+
"commit-search-depth": 10
2425
},
2526
"libs/server-sent-events": {
2627
"initial-version": "0.1.0"

0 commit comments

Comments
 (0)