Open sau226 opened 3 years ago
Is this still an issue?
Given that it still says that the last publish was 0.8.0
2 years ago, I'd say it still is
From the GitHub packages documentation:
You can use an .npmrc file to configure the scope mapping for your project. In the .npmrc file, use the GitHub Packages URL and account owner so GitHub Packages knows where to route package requests. Using an .npmrc file prevents other developers from accidentally publishing the package to npmjs.org instead of GitHub Packages.
Oops I guess...
The co-design package on GitHub packages (https://github.com/codidact/co-design/packages/245635) is obviously not in sync with the version published on NPM (https://www.npmjs.com/package/@codidact/co-design). Specifically, the GitHub packages version is 0.8.0, but the NPM one says version 0.12.0 is published.
Could we fix the package on GitHub by either: 1) Altering any release scripts to push to GitHub packages as well as npm and pushing say the last released version (as of this issue) to GitHub packages 2) Taking down the package from GitHub packages (maybe by making the repo private, taking the package down, and then marking it public again?)
This ensures consistency across platforms and ensures that clients will always be able to fetch the actual latest version of this package. Thanks!