{"action":"created","issue":{"url":"https://api.github.com/repos/semantic-release/semantic-release/issues/165","labels_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/165/labels{/name}","comments_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/165/comments","events_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/165/events","html_url":"https://github.com/semantic-release/semantic-release/issues/165","id":124949587,"number":165,"title":"Merging pull requests in quick succession causes conflated releases","user":{"login":"tlvince","id":323761,"avatar_url":"https://avatars.githubusercontent.com/u/323761?v=3","gravatar_id":"","url":"https://api.github.com/users/tlvince","html_url":"https://github.com/tlvince","followers_url":"https://api.github.com/users/tlvince/followers","following_url":"https://api.github.com/users/tlvince/following{/other_user}","gists_url":"https://api.github.com/users/tlvince/gists{/gist_id}","starred_url":"https://api.github.com/users/tlvince/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tlvince/subscriptions","organizations_url":"https://api.github.com/users/tlvince/orgs","repos_url":"https://api.github.com/users/tlvince/repos","events_url":"https://api.github.com/users/tlvince/events{/privacy}","received_events_url":"https://api.github.com/users/tlvince/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-05T11:44:24Z","updated_at":"2016-01-05T11:46:00Z","closed_at":null,"body":"Say a project has three pull requests open with three `fix` commits. If all pull requests are merged in quick succession, each resulting release will contain the commits merged before it. For example:\r\n\r\n`1.0.0`\r\n* Commit A\r\n\r\n`1.0.1`\r\n* Commit B\r\n* Commit A\r\n\r\n`1.0.2`\r\n* Commit C\r\n* Commit B\r\n* Commit A\r\n\r\nUnfortunately, I don't have a reduced test case for this yet, but we've noticed this in a production app (unfortunately closed source). Will provide more detail later.\r\n\r\n`semantic-release` v4.3.5, Node 4.x."},"comment":{"url":"https://api.github.com/repos/semantic-release/semantic-release/issues/comments/168979229","html_url":"https://github.com/semantic-release/semantic-release/issues/165#issuecomment-168979229","issue_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/165","id":168979229,"user":{"login":"tlvince","id":323761,"avatar_url":"https://avatars.githubusercontent.com/u/323761?v=3","gravatar_id":"","url":"https://api.github.com/users/tlvince","html_url":"https://github.com/tlvince","followers_url":"https://api.github.com/users/tlvince/followers","following_url":"https://api.github.com/users/tlvince/following{/other_user}","gists_url":"https://api.github.com/users/tlvince/gists{/gist_id}","starred_url":"https://api.github.com/users/tlvince/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tlvince/subscriptions","organizations_url":"https://api.github.com/users/tlvince/orgs","repos_url":"https://api.github.com/users/tlvince/repos","events_url":"https://api.github.com/users/tlvince/events{/privacy}","received_events_url":"https://api.github.com/users/tlvince/received_events","type":"User","site_admin":false},"created_at":"2016-01-05T11:46:00Z","updated_at":"2016-01-05T11:46:00Z","body":"Note, I suspect this might be happening because Travis hasn't yet finished the previous build/semantic-release pushed a release. Perhaps limiting Travis' [concurrent jobs](https://docs.travis-ci.com/user/customizing-the-build/#Limiting-Concurrent-Builds) to 1 would fix this?"}}