#semver — Public Fediverse posts

I spent most of this year so far figuring out possible designs to solve those problems.

RustWeek + All Hands were phenomenally useful! I worked w/ rustdoc, types, compiler, cargo, and other folks to poke holes in the designs and then patch them.

Thank you @rustnl for making it happen!

#rust #rustlang #semver #rustweek #rustweek2026

I spent most of this year so far figuring out possible designs to solve those problems.

RustWeek + All Hands were phenomenally useful! I worked w/ rustdoc, types, compiler, cargo, and other folks to poke holes in the designs and then patch them.

Thank you @rustnl for making it happen!

#rust #rustlang #semver #rustweek #rustweek2026

I spent most of this year so far figuring out possible designs to solve those problems.

RustWeek + All Hands were phenomenally useful! I worked w/ rustdoc, types, compiler, cargo, and other folks to poke holes in the designs and then patch them.

Thank you @rustnl for making it happen!

#rust #rustlang #semver #rustweek #rustweek2026

I spent most of this year so far figuring out possible designs to solve those problems.

RustWeek + All Hands were phenomenally useful! I worked w/ rustdoc, types, compiler, cargo, and other folks to poke holes in the designs and then patch them.

Thank you @rustnl for making it happen!

#rust #rustlang #semver #rustweek #rustweek2026

I spent most of this year so far figuring out possible designs to solve those problems.

RustWeek + All Hands were phenomenally useful! I worked w/ rustdoc, types, compiler, cargo, and other folks to poke holes in the designs and then patch them.

Thank you @rustnl for making it happen!

#rust #rustlang #semver #rustweek #rustweek2026

I'm working on cargo-semver-checks, and I realized that an edge case of one of my edge cases has an edge case that breaks my planned design.

That means that so far, I'm having an average Saturday in cargo-semver-checks land 😅

#semver #rust #rustlang

Was that change really a patch—or did you just break someone’s build? Manual #SemVer is fragile, especially in growing teams. @JagoVreede enforces it with code.

Make your versions trustworthy again and avoid hidden breaking changes: https://javapro.io/2026/03/26/semantic-versioning-done-automatically/

#Java #Maven #API

#semver anyone? Semantic versioning like

3.14.1 as major.minor.patch

is defined on https://semver.org/ with

PATCH version when you make backward compatible bug fixes

What is a "backward compatible bug fix"? After a bug fix, the software is no longer compatible with the buggy version, ON PURPOSE. Any dependent software which accommodates so far to the bug may now have problems?

What am I missing?

#npm #java #javascript #programming #softwaredevelopment

Finally finished that SemVer rant. Say no to ZeroVer: https://blog.nytsoi.net/2026/04/03/say-no-to-zero-ver/

#SemVer #programming

Was that change really a patch—or did you just break someone’s build? Manual #SemVer is fragile, especially in growing teams. @JagoVreede enforces it with code.

Make your versions trustworthy again and avoid hidden breaking changes: https://javapro.io/2026/03/26/semantic-versioning-done-automatically/

#Java #Maven #API

I also fixed the rustdoc bug upstream!
https://github.com/rust-lang/rust/pull/153465/

#rust #rustlang #semver

cargo-semver-checks v0.47 is live now ✨

Inside, you'll find:
- a workaround for a Rust 1.94 rustdoc bug that caused crashes in some projects
- 7 new lints

Happy SemVer Sunday!
https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.47.0

#rust #rustlang #semver

#SemVer! #DateVer! #MonotonicVer!

There are lots of #options, so following rule 927, I hereby propose my own #alternative.

#SpiralVer!

v. 1
v. j1
v. -1
v. -j1
v. 2
v. j2
[...]

One problem is that minor releases require doing #trigonometry.

#XKCD927 #standards #versioning #mathematics #complex #ComplexNumbers #engineering #trigonometry #sin #cosin

#SemVer! #DateVer! #MonotonicVer!

There are lots of #options, so following rule 927, I hereby propose my own #alternative.

#SpiralVer!

v. 1
v. j1
v. -1
v. -j1
v. 2
v. j2
[...]

One problem is that minor releases require doing #trigonometry.

#XKCD927 #standards #versioning #mathematics #complex #ComplexNumbers #engineering #trigonometry #sin #cosin

#SemVer! #DateVer! #MonotonicVer!

There are lots of #options, so following rule 927, I hereby propose my own #alternative.

#SpiralVer!

v. 1
v. j1
v. -1
v. -j1
v. 2
v. j2
[...]

One problem is that minor releases require doing #trigonometry.

#XKCD927 #standards #versioning #mathematics #complex #ComplexNumbers #engineering #trigonometry #sin #cosin

#SemVer! #DateVer! #MonotonicVer!

There are lots of #options, so following rule 927, I hereby propose my own #alternative.

#SpiralVer!

v. 1
v. j1
v. -1
v. -j1
v. 2
v. j2
[...]

One problem is that minor releases require doing #trigonometry.

#XKCD927 #standards #versioning #mathematics #complex #ComplexNumbers #engineering #trigonometry #sin #cosin

#SemVer! #DateVer! #MonotonicVer!

There are lots of #options, so following rule 927, I hereby propose my own #alternative.

#SpiralVer!

v. 1
v. j1
v. -1
v. -j1
v. 2
v. j2
[...]

One problem is that minor releases require doing #trigonometry.

#XKCD927 #standards #versioning #mathematics #complex #ComplexNumbers #engineering #trigonometry #sin #cosin

Blogged : update semantic version using #bash script

https://blog.revathskumar.com/2026/02/update-semantic-version-using-bash-script.html

#zig #GithubAction #semver

Handling Breaking Changes in a Design System Without Causing Chaos, by @shaunbent (@zeroheight):

https://zeroheight.com/blog/handling-breaking-changes-in-a-design-system-without-causing-chaos/

#designsystems #maintenance #semver #communication

I realize that I might have misused the "semantic versioning" with the last release of Back In Time.
Compared to 1.5.6, there are so many breaking changes in 1.6.0, that it better should have been 2.0.0.

What do you think?

https://github.com/bit-team/backintime/blob/dev/CHANGES

#semver #release #foss #opensource #gnu #debian #arch

@douginamug well, the versioning being #semver, the major version number had to be bumped to drop support for NodeJS before v20.12.0 (= breaking change), to use the new native `styleText` util function https://nodejs.org/api/util.html#utilstyletextformat-text-options , not exactly the most epic major version 😅

Fighting my #Hauptversionsnummererhöhungangst 😁

@matildalove @wyatt I too have used date-based version numbering for some projects. It works well for things with a regular release cadence, such as semiannual tracks of Ubuntu and Windows 10 and 11. It's good for some cases but has drawbacks for others.
- Library users prefer SemVer, which increases the first part on a breaking change.
- Software subject to a service level agreement tends to increase the first part when licensees of the previous version must pay for an upgrade.

#semver #versionnumbering #ubuntu #windows10 #windows11

And in case you missed it, here's our annual recap and our plans for 2026, which should look somewhat different than the last few years!
https://hachyderm.io/@predrag/115878287653426956

#rust #rustlang #semver

cargo-semver-checks v0.46 was released earlier this week ✨

It comes with 45 *new* lints. Almost 20% of *all lints* are new in this release — this is wild!! Exponential growth, manifested.
https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.46.0

#rust #rustlang #semver

Shout-outs to the kind folks who make this work possible by funding cargo-semver-checks 🙏

#rust #rustlang #semver #yearinreview

I also propose a change in how we measure success going forward.

I hate gameable metrics. Let's build what's most valuable for the community, not what's easiest to quantify and brag about.

Does this resonate? Let me know what you think!

Bonus points if you also fund cargo-semver-checks, of course!

#rust #rustlang #semver #yearinreview

Here's everything you'll find in the post above!

If you're a regular reader, some of these sections may be familiar. There are links so you can skip ahead!

#rust #rustlang #semver #yearinreview

cargo-semver-checks is growing faster than ever:
- 7 new releases, from v0.39 to v0.45
- 122 new lints, more than double last year's count
- 4x reduction in lint execution time — some lints became up to 10x faster
- across 26 (!!) rustdoc format versions

Check out our "year in review" 👇
https://predr.ag/blog/cargo-semver-checks-2025-year-in-review/

#rust #rustlang #semver #yearinreview

Мифы об обратной совместимости

В любой дискуссии о версионировании — самые горячие споры обычно ведутся вокруг надуманной проблемы: «как нам при помощи правильной заверсионированности нивелировать нерадивость и низкую компетенцию наших сотрудников, не способных создавать обратно-совместимый код?». Эти споры не сто́ят выеденного яйца

https://habr.com/ru/articles/983178/

#semver #versioning #semantic_versioning #версионирование #версии

Эволюция методологий версионирования

Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

https://habr.com/ru/articles/982740/

#EvoVer #SemVer #CalVer #версионирование #версия

Эволюция методологий версионирования

Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

https://habr.com/ru/articles/982740/

#EvoVer #SemVer #CalVer #версионирование #версия

Эволюция методологий версионирования

Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

https://habr.com/ru/articles/982740/

#EvoVer #SemVer #CalVer #версионирование #версия

Эволюция методологий версионирования

Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

https://habr.com/ru/articles/982740/

#EvoVer #SemVer #CalVer #версионирование #версия

SemVer is tricky in all languages. But in Rust, it's easier than ever before!

By the end of 2024, cargo-semver-checks' capabilities were growing exponentially: 30 -> 57 -> 120 lints.

We now end 2025 with 242 lints — 122 new lints were merged this calendar year 🎉 The exponential continues!

#rust #rustlang #semver

I finally got annoyed enough with the #zerover limbo that I slapped on a v1.0.0 tag and switched to #semver for my #git utility that sets filesystem modification timestamps to the last commit that touched each file in a repository:

https://github.com/alerque/git-warp-time

No big changes, just an indication that the tool works and there is no need on the horizon to shake it up.

If you use a build system like #make that reacts to timestamps and are tired of wasted builds jump in; the water is clear of sharks.

@brettcannon

In your specific example, assuming the project is using https://semver.org/, I would reevaluate - thinking I got it wrong since I know you are so much more experienced than me.

However, my main reason for making it show easier, including for the --version, is that there are a lot of x.y.z projects that isn't #SemVer.

https://packaging.python.org/en/latest/specifications/version-specifiers/#version-specifiers list quite a few.

What if pyproject.toml had something like:

[project]
name = "demo"
version-scheme = "SemVer 2.0.0"
version = "0.1.0"

@brettcannon

Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

> python -V
Python 3.13.7 SemVer 2025-08-14

@brettcannon

Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

> python -V
Python 3.13.7 SemVer 2025-08-14

@brettcannon

Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

> python -V
Python 3.13.7 SemVer 2025-08-14

@brettcannon

Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

> python -V
Python 3.13.7 SemVer 2025-08-14

@brettcannon

Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

> python -V
Python 3.13.7 SemVer 2025-08-14

Major Version Numbers are Not Sacred

http://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
https://app.flus.fr/links/1849140301341160978

#dev #semver

cargo-semver-checks v0.45.0 is out today 🎉

ICYMI, this post discusses how the headline feature came about: support for users' local `.cargo/config.toml` configuration.

"How hard could supporting configuration be?" you say? Read the post, then tell me 😁
https://predr.ag/blog/ghosts-in-the-compilation/

#rust #rustlang #semver

I ran into some ghosts when compiling Rust:
- `cargo-semver-checks` said the code didn't compile.
- `cargo check` said it was fine.

What better day to talk about it than Halloween? 🎃👻

https://predr.ag/blog/ghosts-in-the-compilation/

#rust #rustlang #semver #halloween

I'm not sure I understand `cargo semver-checks`. I have a crate published to crates.io with a public struct. I change the type of a public field inside that struct. A subsequent run of `cargo semver-checks` just says "no change; assume minor" for that crate. What's the point of this tool if it doesn't even highlight that really obvious semver breaking change? Or am I just holding it wrong?

#rustlang #semver

Which npm Package Has the Largest Version Number?, by (not on Mastodon or Bluesky):

https://adamhl.dev/blog/largest-number-in-npm-package/

#npm #dependencies #versioning #semver

Speeding Up the JavaScript Ecosystem—SemVer, by @marvinh:

https://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-12/

#javascript #performance #semver #versioning #dependencies

just got some spare time and pushed a bunch of fixes to obsidian-typewriter (https://github.com/crashmoney/obsidian-typewriter). obsidian users, update your theme to see the fixes – lots of them are small pet peeves and minor bugs :)

i also opened a ko-fi for those enjoying the theme & wishing to tip! the link is on my profile and here: https://ko-fi.com/crashmoney7

bumped up my version of semantic versioning to v2.2 as well. now back to work…

#obsidian #ObsidianMD @obsidian #CSS #tech #FOSS #ObsidianTheme #updates #semver #kofi

just got some spare time and pushed a bunch of fixes to obsidian-typewriter (https://github.com/crashmoney/obsidian-typewriter). obsidian users, update your theme to see the fixes – lots of them are small pet peeves and minor bugs :)

i also opened a ko-fi for those enjoying the theme & wishing to tip! the link is on my profile and here: https://ko-fi.com/crashmoney7

bumped up my version of semantic versioning to v2.2 as well. now back to work…

#obsidian #ObsidianMD @obsidian #CSS #tech #FOSS #ObsidianTheme #updates #semver #kofi

just got some spare time and pushed a bunch of fixes to obsidian-typewriter (https://github.com/crashmoney/obsidian-typewriter). obsidian users, update your theme to see the fixes – lots of them are small pet peeves and minor bugs :)

i also opened a ko-fi for those enjoying the theme & wishing to tip! the link is on my profile and here: https://ko-fi.com/crashmoney7

bumped up my version of semantic versioning to v2.2 as well. now back to work…

#obsidian #ObsidianMD @obsidian #CSS #tech #FOSS #ObsidianTheme #updates #semver #kofi