Skip to content

First repository update after git package rename uses stale state #6782

@arozovyk

Description

@arozovyk

Discovered while working on #6754 -> #6774

After renaming a package version in a git repository, seems like opam doesn't invalidate its cache on the first update. When resolving dependencies, it incorrectly shows the old version will be installed, even though only the new version exists. A second update is needed to see the correct version (given that 00 is resolved as 0).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions