Updating the CE dependency
CE imports retain gitlab.com/bitspur/selfhosted-cloud/ce. Root, tests and
Terraform provider each replace it with the same version of
git.corp.bitspur.com/selfhostedcloud.org/ce.git. The .git suffix lets Go
fetch corporate Git directly without legacy-host module discovery. Go computes
the archive checksums; a replacement’s checksum differs from the old module’s
because its ZIP entry prefixes include the replacement path.
Run make ce/bump CE_SHA=<published-commit> to resolve corporate CE, update all
three modules and regenerate the existing docs, client and default mirror.
make ce/latest does the same for corporate main. Retries rerun generation.
Commit the module files and generated results together.
make ce/verify refuses requirement, replacement or checksum drift, then
downloads and verifies each module with GOWORK=off. Follow with
go build ./..., make test/unit and the focused CE corpus for the change.
The bump also runs the standalone provider build and vet checks.
The existing CI Go anchor uses its job token only for the corporate CE
repository through a process-local Git credential helper. It preserves inherited
Git configuration and writes no netrc or global Git configuration. Branch jobs
follow corporate main through make ce/pin; CE_TRACK=pin freezes branches.
Tags always use the committed replacement.
Corporate CE read permission for the CI job token must be verified by an
authorized pipeline. Local Git access and synthetic helper tests don’t prove it.
For a cold fetch check in that job, set CE_TRACK=pin before the anchor, use a
fresh private GOMODCACHE, and run GOWORK=off go mod download -json gitlab.com/bitspur/selfhosted-cloud/ce. Verify the reported corporate path,
version and checksums against all three committed modules before building.