Skip to content

fix(retract): preserve full phantom tag prefixes - #4886

Merged
asim merged 1 commit into
masterfrom
codex/4884-preserve-phantom-tag-prefixes
Aug 12, 2026
Merged

fix(retract): preserve full phantom tag prefixes#4886
asim merged 1 commit into
masterfrom
codex/4884-preserve-phantom-tag-prefixes

Conversation

@asim

@asim asim commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary

  • only strip an exact /vN/ semantic-major directory from phantom module paths
  • preserve lookalike prefixes such as v2client, v4.0.0, and v5-plugins when constructing retraction tags

Testing

  • bash -n retract-phantom.sh
  • ./retract-phantom.sh --dry-run
  • go build ./...
  • go test ./...

Follow-up to #4884.
Closes #4884

@asim asim added the codex label Aug 12, 2026
Copilot AI lite review requested due to automatic review settings August 12, 2026 09:27
@asim asim added the codex label Aug 12, 2026
@asim
asim merged commit 7a8a13a into master Aug 12, 2026
13 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates retract-phantom.sh to compute module-relative paths more precisely so retraction tags only strip a true semantic-major directory (/vN/) and preserve lookalike prefixes (e.g., v2client, v4.0.0, v5-plugins). This supports the ongoing effort to publish correct “phantom module” retraction tags so proxy-cached bad module paths don’t remain installable.

Changes:

  • Add module_relative_path() helper to strip only go-micro.dev/vN/ when it’s an exact major-version directory.
  • Replace duplicated case-based prefix stripping in both the sanity-check loop and tag construction loop with the new helper.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants