🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.
When publishing packages that have a custom publish_to url that contains a path (e.g. www.customurl.com/custom/path/), reading the current versions of the packages from the repository/registry does not work.
As far as I can tell code around line no. ~901 in package.dart is the reason.
final pubHosted = publishTo ?? pubUrl;
final url = pubHosted.replace(path: '/api/packages/$name');
Is there any reason that path is not just appended instead of replacing?
Steps to reproduce
Create a package with a publish_to url that has a path in it
Publish a version
Make changes and try to publish another version
Reading the registry version will fail
Expected behavior
Show the proper registry versions no matter what the package's publish_to url is.
Is there an existing issue for this?
Version
3.0.0
Description
When publishing packages that have a custom
publish_tourl that contains a path (e.g. www.customurl.com/custom/path/), reading the current versions of the packages from the repository/registry does not work. As far as I can tell code around line no. ~901 in package.dart is the reason.Is there any reason that path is not just appended instead of replacing?
Steps to reproduce
publish_tourl that has a path in itExpected behavior
Show the proper registry versions no matter what the package's
publish_tourl is.Screenshots
No response
Additional context and comments
No response