{"action":"created","issue":{"url":"https://api.github.com/repos/electron/electron/issues/5561","repository_url":"https://api.github.com/repos/electron/electron","labels_url":"https://api.github.com/repos/electron/electron/issues/5561/labels{/name}","comments_url":"https://api.github.com/repos/electron/electron/issues/5561/comments","events_url":"https://api.github.com/repos/electron/electron/issues/5561/events","html_url":"https://github.com/electron/electron/issues/5561","id":155218712,"number":5561,"title":"Is Electron following semver?","user":{"login":"mafintosh","id":376661,"avatar_url":"https://avatars.githubusercontent.com/u/376661?v=3","gravatar_id":"","url":"https://api.github.com/users/mafintosh","html_url":"https://github.com/mafintosh","followers_url":"https://api.github.com/users/mafintosh/followers","following_url":"https://api.github.com/users/mafintosh/following{/other_user}","gists_url":"https://api.github.com/users/mafintosh/gists{/gist_id}","starred_url":"https://api.github.com/users/mafintosh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mafintosh/subscriptions","organizations_url":"https://api.github.com/users/mafintosh/orgs","repos_url":"https://api.github.com/users/mafintosh/repos","events_url":"https://api.github.com/users/mafintosh/events{/privacy}","received_events_url":"https://api.github.com/users/mafintosh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/electron/electron/labels/discussion","name":"discussion","color":"009800"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":21,"created_at":"2016-05-17T09:48:57Z","updated_at":"2016-05-18T00:30:27Z","closed_at":null,"body":"When developing apps for Electron I usually use [electron-prebuilt](https://github.com/electron-userland/electron-prebuilt) with npm and a semver to track updates. This makes it easier for me to update to newer versions of Electron without worrying too much about my app breaking.\r\n\r\nHowever I just noticed that 1.0.2 was recently released and contained new features compared to 1.0.1, https://github.com/electron/electron/releases/tag/v1.0.2 and not just bug fixes.\r\n\r\nDoes this mean Electron isn't following semver? If so I'd like to know so I can start pinning the dependency."},"comment":{"url":"https://api.github.com/repos/electron/electron/issues/comments/219893626","html_url":"https://github.com/electron/electron/issues/5561#issuecomment-219893626","issue_url":"https://api.github.com/repos/electron/electron/issues/5561","id":219893626,"user":{"login":"zcbenz","id":639601,"avatar_url":"https://avatars.githubusercontent.com/u/639601?v=3","gravatar_id":"","url":"https://api.github.com/users/zcbenz","html_url":"https://github.com/zcbenz","followers_url":"https://api.github.com/users/zcbenz/followers","following_url":"https://api.github.com/users/zcbenz/following{/other_user}","gists_url":"https://api.github.com/users/zcbenz/gists{/gist_id}","starred_url":"https://api.github.com/users/zcbenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zcbenz/subscriptions","organizations_url":"https://api.github.com/users/zcbenz/orgs","repos_url":"https://api.github.com/users/zcbenz/repos","events_url":"https://api.github.com/users/zcbenz/events{/privacy}","received_events_url":"https://api.github.com/users/zcbenz/received_events","type":"User","site_admin":true},"created_at":"2016-05-18T00:30:27Z","updated_at":"2016-05-18T00:30:27Z","body":"Chrome upgrades are breaking changes, every time we upgrade Chrome version there are crashes and regressions, so if we follow semver it has to bump the major version. The same goes for Node upgrades, and probably toolchain upgrades (like from Visual Studio 2013 to 2015).\r\n\r\nThe problem with following semver is, we will not be able to distinguish Electron API changes from dependencies upgrades, all of them are bumping major versions. They are two different levels of changes, you have to modify your app for Electron API changes, while you can probably just do nothing to get Chrome upgrades.\r\n\r\nKeep current version scheme but bump minor version for new features, is nice but doesn't quite suit Electron's current situation. For most releases of Electron we are adding new features, so if we use this rule there will basically be no patch version bumps, and users will not be able to judge whether it is safe to upgrade Electron when there are minor version bumps. "}}