fix(ci): point changelog compare links at our Gitea
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m10s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 6s
PR Check / AI code review (opencode) (pull_request) Successful in 22s
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m10s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 6s
PR Check / AI code review (opencode) (pull_request) Successful in 22s
The generated CHANGELOG linked every release to github.com/CV_Website/CV_Site_Nuxt, a host this repository does not live on. release-please takes the compare host from the configuration, so it is set now. The decision record also gains the real reason no tag was ever created: Gitea rewrites a merged PR's head.ref to refs/pull/<n>/head once the head branch is deleted, and the Gitea build parses that field as the release branch. BranchName.parse then fails and the release is dropped with a logged error while the run still exits 0. The repository deleted every merged branch; that default is off now, and the versions the manifest already consumed have to be tagged by hand.
This commit is contained in:
1 parent
0c937e6f80
commit
a2259df877
3 files changed
+51
-16
No files matched your search
@@ -3,6 +3,7 @@
|
||||
"release-type": "node",
|
||||
"include-component-in-tag": false,
|
||||
"separate-pull-requests": false,
|
||||
"changelog-host": "https://git.noelsabia.dev",
|
||||
"packages": {
|
||||
".": {
|
||||
"package-name": "CV_Site_Frontend",
|
||||
|
||||
Reference in new issue
Block a user