Replies: 4 comments
-
I think I know why, the scope of the package needs to match the organization.. kinda out of left field there and is not as streamlined as npm :( will test to setup a new org to see if that helps. Not closing until I have verification |
Beta Was this translation helpful? Give feedback.
-
Nope that did not work. I have moved my repo to an organisation: {
"publishConfig": {
"@knowitlabs:registry": "https://npm.pkg.github.com/knowitlabs"
},
} Getting grey hairs now :/ |
Beta Was this translation helpful? Give feedback.
-
From what I can dig up, lerna/libs/commands/publish/src/index.ts Line 666 in 4fb0427 I publish with the command: |
Beta Was this translation helpful? Give feedback.
-
Solved with #3745 (comment) |
Beta Was this translation helpful? Give feedback.
-
Something stumps me, lerna states that
All packages have already been published
, no errors, nothing to use from higher log level, and no packages are found in the github packages system.I am using
lerna@7.0.2
, all packages has got the required settings:Using this command:
I use a
.npmrc
-file with the required access token for github, with the correct permissions.Beta Was this translation helpful? Give feedback.
All reactions