Skip to content

ci: move base14 release pipeline out of the fork - #1

Merged
thilak009 merged 1 commit into
masterfrom
ci/move-base14-release-out
Oct 8, 2026
Merged

thilak009 merged 1 commit into
masterfrom
ci/move-base14-release-out

Conversation

@thilak009

Copy link
Copy Markdown

Summary

This fork is public, and so are its Actions logs. The base14 release pipeline had ECR, AWS role and self-hosted runner details in it, so it now lives in the private base14-infra repo (chproxy-release.yml, plus a runbook in docs/runbooks/chproxy-release.md). The fork keeps only upstream code and our patches.

  • Remove .github/workflows/base14-release.yml and RELEASE.md.
  • release.yml: keep the !*-b14.* tag exclusion so upstream's goreleaser ignores base14 tags; update its comment, which pointed at the removed workflow.
  • go-test.yaml: run the coverage-report step only on ContentSquare/chproxy. On the fork it tried to push to a wiki that doesn't exist (repository 'https://github.com/base-14/chproxy.wiki/' not found), so go-test failed on master even though the tests passed.

Related: B14-2392

@thilak009
thilak009 merged commit 3c99b5f into master Oct 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant