| ▲ | kuschku a day ago | |||||||||||||||||||||||||
You mention semver, yet you also show that this API breaking change was introduced in a minor version. Not entirely sure that's how things work? | ||||||||||||||||||||||||||
| ▲ | r3trohack3r a day ago | parent [-] | |||||||||||||||||||||||||
You're not wrong - the semver doesn't indicate a breaking API change. But, to be fair, this wasn't a breaking API change. Any consumer of this software using it for its intended purpose (S3) didn't need to make any changes to their code when upgrading to this version. As an AWS customer, knowing that when I I upgrade to this version my app will continue working without any changes is exactly what this semver bump communicates to me. I believe calling this a feature release is correct. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||