{"action":"opened","issue":{"url":"https://api.github.com/repos/lerna/lerna/issues/660","repository_url":"https://api.github.com/repos/lerna/lerna","labels_url":"https://api.github.com/repos/lerna/lerna/issues/660/labels{/name}","comments_url":"https://api.github.com/repos/lerna/lerna/issues/660/comments","events_url":"https://api.github.com/repos/lerna/lerna/issues/660/events","html_url":"https://github.com/lerna/lerna/issues/660","id":213234220,"number":660,"title":"Not all package peer/dev deps were updated during a publish","user":{"login":"milesj","id":143744,"avatar_url":"https://avatars1.githubusercontent.com/u/143744?v=3","gravatar_id":"","url":"https://api.github.com/users/milesj","html_url":"https://github.com/milesj","followers_url":"https://api.github.com/users/milesj/followers","following_url":"https://api.github.com/users/milesj/following{/other_user}","gists_url":"https://api.github.com/users/milesj/gists{/gist_id}","starred_url":"https://api.github.com/users/milesj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/milesj/subscriptions","organizations_url":"https://api.github.com/users/milesj/orgs","repos_url":"https://api.github.com/users/milesj/repos","events_url":"https://api.github.com/users/milesj/events{/privacy}","received_events_url":"https://api.github.com/users/milesj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-10T03:33:29Z","updated_at":"2017-03-10T03:33:29Z","closed_at":null,"body":"Project and packages here: https://github.com/milesj/aesthetic/tree/master/packages\r\n\r\nI just ran `lerna publish --include-filtered-dependencies --force-publish=*` to update all packages major version to 1.0.0 (which tagged successfully). However, I noticed after the fact, that the `peerDependencies` and `devDependencies` for `aesthetic-adapter-css-modules` and `aesthetic-adapter-jss` did not update to the 1.0.0 version, while all the other packages did, but instead remained on the previous version of 0.5.2. I tried publishing a 1.0.1 version and the same exact thing happened.\r\n\r\nI'm not entirely sure what the root cause is. Could it be that the source files are not directly in the packages folder (I build to them)? That wouldn't explain the inconsistency though."}}
{"actor":{"display_login":"milesj"}}