Repository navigation
fix: organisation rename - #86
shevchenkov-neuralegion wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
First, according to our contributing guide, conventional commits, and semver, this change should not be classified as fix.
Second, since the commit is marked as a fix, it will trigger a release. However, you are also changing the package scope, and the package doesn't currently exist under the new scope. Trusted publishing hasn't been configured either, which means the release will fail.
Before merging, you need to manually publish the existing package version under the new scope, configure trusted publishing, and verify that everything is set up correctly. Only then should this PR be merged.
P.S. PR should have labels assigned
|
Agreed to not migrate cli sub-packages as of now. Closing it. |
|
@shevchenkov-neuralegion when are you planning to do this, and are there any tickets tracking it? If not, please create them and prioritize accordingly. |
|
@derevnjuk as its not critical to make cli works, I've planned it for the next sprint as well as raw-socket |
No description provided.