Skip to content

fix: retract old versions with mismatched module path #929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cpcloud wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: retract old versions with mismatched module path #929

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dc82ecf
fix: retract old versions with mismatched module path
cpcloud Apr 14, 2026
27a7207
docs: add license header to spec file
cpcloud Apr 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions go.mod
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,13 @@ module github.com/micasa-dev/micasa

go 1.26

// Pre-v2.4.0 versions declared module path github.com/cpcloud/micasa
// which conflicts with the current github.com/micasa-dev/micasa path.
// The v2.x tags also used the old path without a /v2 suffix, so Go
// treats them as a different module entirely; only v1.x is retractable
// from this module.
retract [v1.0.0, v1.80.0]

require (
charm.land/fang/v2 v2.0.1
github.com/BurntSushi/toml v1.6.0
Expand Down
44 changes: 44 additions & 0 deletions plans/923-installation-error.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
<!-- Copyright 2026 Phillip Cloud -->
<!-- Licensed under the Apache License, Version 2.0 -->

# Issue #923: `go install` error

## Root cause

The repository was migrated from `github.com/cpcloud/micasa` to
`github.com/micasa-dev/micasa`. Old version tags (v1.0.0 through v1.80.0 and
v2.0.0 through v2.3.0) still have `module github.com/cpcloud/micasa` in their
`go.mod`. When a user runs:

```sh
go install github.com/micasa-dev/micasa/cmd/micasa@latest
```

Go resolves `@latest` and finds these old tags. The mismatch between the
requested module path (`github.com/micasa-dev/micasa`) and the module path
declared in the old tags (`github.com/cpcloud/micasa`) causes Go to error.

## Fix

Add a `retract` directive to `go.mod` covering the v1.x range:

```go
retract [v1.0.0, v1.80.0]
```

This tells Go to skip those versions when resolving `@latest`.

The v2.x tags (v2.0.0 through v2.3.0) also declared
`module github.com/cpcloud/micasa` without a `/v2` suffix. Because the module
path differs, Go treats them as a completely different module -- they do not
conflict with `github.com/micasa-dev/micasa` and cannot be retracted from this
module's `go.mod`.

Starting from v2.4.0, all tags use the correct module path
`github.com/micasa-dev/micasa`, so no further action is needed.

## What was NOT changed

- Module path stays `github.com/micasa-dev/micasa` (no `/v2` suffix)
- No import path changes anywhere in the codebase
- Install docs already used `@latest`, no changes needed
Loading