Skip to content

Rename module path zos4 -> zos_v4 (match repo, off redirect) - #34

Merged
ashraffouda merged 2 commits into
mainfrom
rename-module-zos4-to-zos-v4
Jul 15, 2026
Merged

Rename module path zos4 -> zos_v4 (match repo, off redirect)#34
ashraffouda merged 2 commits into
mainfrom
rename-module-zos4-to-zos-v4

Conversation

@ashraffouda

Copy link
Copy Markdown
Collaborator

Renames the Go module path github.com/threefoldtech/zos4 -> github.com/threefoldtech/zos_v4 to match the renamed repo, off the zos4->zos_v4 rename redirect and out of the module-path collision with zos_light (which also wrongly declared .../zos4). Covers the main module + the nested tools/zos-update-version module directives, internal imports (gofmt'd), and Makefile ldflags. Both modules build. The zosbase dependency is left at v1.0.3 (the zos_base@v1.1.0 migration is deferred separately due to Provision.ListTwins API drift). Part of #2693.

The repo was renamed zos4 -> zos_v4, but the module still declared
github.com/threefoldtech/zos4, which relies on the (non-permanent) rename
redirect and collides with zoslight/zos_light. Rename the main + nested
(tools/zos-update-version) module directives, internal imports, and
Makefile ldflags to github.com/threefoldtech/zos_v4. Both modules build.
The zosbase dependency is left at v1.0.3 (separate, deferred migration).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The Set up Go step (setup-go@v1) fails on the current GitHub host runner,
blocking Build and upload / Running Daemon Tests before the module-rename build
runs. Bump to v5. Container builders untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ashraffouda
ashraffouda merged commit ee82e13 into main Jul 15, 2026
23 of 24 checks passed
@ashraffouda
ashraffouda deleted the rename-module-zos4-to-zos-v4 branch July 15, 2026 09:14
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