Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • 4
    Who is consuming that semantic version? Commented Jun 17, 2022 at 10:10
  • My app is for end users, I have no "real" API people will have to rely on if that's what you mean. I know it's not that important under those circumstances, but I'm new to developing and want to learn it the "right" way from the start : ) Commented Jun 17, 2022 at 10:15
  • The point of semver is that consumers of your API can understand when their use of it may break and they'll need to make changes. If your consumers are end users, semver would likely apply only to the UI, not the technical implementation. Commented Jun 17, 2022 at 10:18
  • Ok, so in my case it would be minor or patch level, as the user wouldn't see anything regarding framework. But suppose I had an API, but wouldn't have to change anything about it when bumping the framework, would that still hold true? Commented Jun 17, 2022 at 10:20
  • 3
    A technology change from .Net Fw 4.8 to 5.0 will definitely cause a breaking change for libraries based on that technology. Commented Jun 17, 2022 at 11:19