Kind of torn on the semantics of #semver

Does a change in behaviour grant a breaking change, if the API remains the same (drop-in upgrade), but the new behaviour seems like a bug fix?

For context: next-usequerystate up to 1.7.3 did scroll to the top of the page on query updates, which was annoying. The new version doesn't.

What version should that be? (there are other features in the release to it'll be at least a minor bump)

#webdev #react #opensource

In Rich Hickey's Specu-lation talk he seems to want to differentiate between removals and other backwards incompatibility changes. I don't really understand his point here. Why separate breaking changes into multiple categories? Link to timestamp https://youtu.be/oyLBGkS5ICk?t=2239

#clojure #semver

Do folks have examples of projects that have performed extremely painful major version bumps in software?

I'm looking for examples like Python 2 to 3.

#software #versioning #semver

If you or your company like cargo-semver-checks, please ✨ sponsor my work on it ✨

With your sponsorship, I could work on:
- catching dozens of new breaking changes
- making perf even faster
- getting it merged into cargo itself

I'd love to make it a project that can help pay my rent, instead of being just a project I poke at in spare time.

💖 RTs highly appreciated 💖

https://github.com/sponsors/obi1kenobi

#rust #rustlang #semver

me dejó correr el proyecto, no sin dejarme una pequeña nota:

warning: parser/current is loading parser/ruby30, which recognizes 3.0.6-compliant syntax, but you are running 3.0.5.

me caga que me rompan cosas en versiones parche. ¿para qué chingaus tenemos #semver entonces?

Taken from https://www.linkedin.com/feed/update/urn:li:activity:7085226364622020609?utm_source=share&utm_medium=member_desktop

#kubernetes #k8s #semver

semver-info-action 1.5.0 🎉 Remove node modules for easier development - Thx to mehdi-ra Try it out! https://github.com/marketplace/actions/semver-info-action #GitHubActions #semantic #workflow #semver #githubactions #githubaction @github

semver-info-action 1.4.0 🎉 Added support for version.txt files for semver comparison. param: 'use-version-txt' Try it out! https://github.com/marketplace/actions/semver-info-action #GitHubActions #semantic #workflow #semver #githubactions #githubaction @github

So, are you more #SemVer or #ZeroVer for your software versioning? Like #reactnative or #hugo

https://0ver.org

After all... even in major versions we encounter breaking changes 🥴

@carlton I agree, as long as it is mentioned in the CHANGELOG.

I would very much prefer increasing the minor of #SemVer when such changes are made.

Worked in my package set.

Due to the change of the constraints around the `Show` instances, I believe this is a MAJOR version change. #SemVer

If you want to add it to your package set you can use:

```
with bound =
{ dependencies =
[ "transformers"
, "bifunctors"
, "foldable-traversable"
, "maybe"
]
, repo = "https://github.com/stephen-smith/purescript-bound.git"
, version = "v1.0.0-nmu.bss.1"
}
```

Pre-release version in case the existing maintainer shows up.

@voxpelli Agree, the appearance of using #semver is the worst part about it - it messes with all assumptions you might have seeing the version.

But I also think semver would still be a good choice!
I don't get why some projects are so afraid of doing major version bumps often. The changes are breaking anyways, it's not like it's more difficult to update because of the major version.
Don't be so afraid of reaching a major version in the two or three digits.

#typescript releases are always weird.

I'm happy that there's something new, but it also makes me angry to be reminded that it doesn't follow #semver.

✨ cargo-semver-checks v0.21 is out ✨

You can *finally* specify which crate features you want checked! This was our most-requested feature!

Also a new lint, better error messages, and more. Release notes here:
https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.21.0

#rustlang #semver

Generar CHANGELOG.md basado en la diferencia de tags de Git

#ChangeLog #Commits #Common #Conventional #Git #Markdown #SCM #SemVer #Tags

https://osiux.com/2023-05-25-git-tag-changelog.html

Incrementar la version de un project o job template de AWX usando awx-json-bump-version

#Ansible #AnsibleTools #AWX #JSON #Release #SemVer

https://osiux.com/2023-05-22-awx-json-bump-version.html

Say I've got a handful of #NPM packages, and they share a few common dependencies, and a list of versions for each package, so:

```
a@1.0.0
a@1.1.0
b@1.0.0
b@1.0.1
```

I need to generate the smallest number of #semver-compatible bundles of the shared dependencies.

So given a list of specific package specs, I need a function that returns a list of highest-semver-compatible dep specs

in: `[ 'a@1.0.0', 'b@2.0.0',]`
out: `['dep-a@1.2.3', 'dep-b@1.1.0']`

Is there already a tool that can do that?

#semver question:

Would you bump the major version for a binary project when you make a library-related change?

e.g. 1.0.0 -> 2.0.0

Assume that you make a breaking change in the library code but main purpose of the project is not to be used as a library.

@tay @aral It’s not the right choice for MegaCorp™️ and their very important customers.

But for as much as I trust $randomProject to follow #semVer and not put breaking changes into v14.7.37-9, a date and a git commit is equally practical to me.

In semantic versioning, if you remove a declared dependency without altering your API, that is:

#SemVer