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

When #semver isn't enough

Tip 89 of #TuesdayCodingTips - Semantic versioning

When creating a library, semantic versioning is a really useful versioning scheme to use.

It's a promise to your users that changes bumping the minor/patch version numbers are backward-compatible. As such, much of the software relies on these numbers to figure out whether a particular version requirement can be satisfied by higher-version binaries.

For example, Unix SONAME links provide a stable way to (typically) reference a major version of a library, while the pointed-to file can be updated to newer revisions.

If you only specify the major (or major.minor) version number, CMake Find* scripts will find the newest compatible package. Various wildcards in cargo, npm, and other package managers follow the same principles.

Just be sure to read the full FAQ at http://semver.org and know that adhering to this versioning scheme is hard, but your users will love you for it... (1/2)

New blog post + cargo-semver-checks v0.42 is out

I found some unexspected sharp edges in the `#[target_feature]` attribute. They are getting fixed (teamwork! ), and cargo-semver-checks now also has lints to save you from footguns!
https://predr.ag/blog/unsoundness-and-accidental-features-in-target-feature/

Rust CLIs with Clap
https://tucson-josh.com/posts/rust-clap-cli/
#ycombinator #rust #clickhouse #sql #software #photography #clap #cli #SemVer

Just found out that #cargo (The #rust thing) is still pre-release software at version 0.88.0…

Kinda not surprising considering that even their #semver implementation isn’t standards-complient and assumes any form of stability guarantees for pre 1.0.0 releases. Sadly it still drives home that the rust ecosystem as a whole is still not ready for actual practical use, because everything seems to depend on unstable pre-release versions.

(Seriously, this #zerover nonsense is a much bigger factor in keeping me away from rust than it probably should be; among many other issues it communicates an extreme disregard for standards and professionalism: Semver explicitly states that “If your software is being used in production, it should probably already be 1.0.0.” — Having widely used software on version 0.x.y is at least as much a semver-violation as a minor breaking change between version 1.1.1 and 1.1.2! Rewriting with a new API in a different programming language between version 0.2.3 and 0.2.4 is btw. NOT a semver-violation, but explicitly allowed!)

Experienced engineers never break SemVer. Nobody needs tools like cargo-semver-checks — just be more careful </s>

I even *had left myself a note* that the next release needs to be a major bump. Too bad I only saw the note after cargo-semver-checks stopped the publish job!

If a software package release contains bug fixes and deprecations, do the deprecations make it a minor release (i.e., new, additive features release), or is it still a patch-level release (i.e., bug fixes only), since there are no new features?

In other words, are deprecations new features?

TIL: #semver (https://semver.org/#spec-item-9) defines a "prerelease" differently than python and dpkg does it:

Semever: 0.1.1-20250101 < 0.1.1 < 0.1.1
debian/python: 0.1.1 < 0.1.1-20250101 < 0.1.2

Why? WHY? WHYYYYY?

Ich habe eine neue Artikel-Reihe gestartet: #Wissensmanagement in der #Architektur

Wie wir mit #AsciiDoc, #Git, #BibTeX und etwas #Perl komplexe Dokumente in der Architektur erstellen und vor allem wiederfinden und #Revisionen tracken.
Außerdem ein paar Punkte warum #MarkDown saugt und #kroki fetzt

https://www.kaishakunin.com/posts/architekturwissensmanagement/01/

New cargo-semver-checks just dropped, enjoy!

And if you're enjoying, please support the project on GitHub Sponsors
https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.41.0

This episode of #OpenSourceSecurity talks to @predrag about cargo-semver-checks

it's a #Rust tool that can help you figure out if you broke #semver, it's pretty awesome

We also touch on the difficulty of detecting breaking changes, sustainable open source, and what's to come for semver checking

It's a fun chat and you'll learn a lot

https://opensourcesecurity.io/2025/2025-04-cargo-semver-checks-predrag-gruevski/

@joshbressers loved the cargo-semver-checks episode. It was neat to see that the problem was way more complex than I understood (definitely dunning Kruger topic for me). But it was even cooler to learn that it could be applied to #python .

My first W3C specification has been posted by the W3C. Super excited, cant wait to get the others in!

https://www.w3.org/submissions/semantic-versioning/

Read more about it here: https://cleverthis.com/news/clever-semantic-versioning-w3c-submission/

cargo-semver-checks v0.40 is out

https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.40.0

I have now installed and tested Authentik for CoreUnit.NET. So far I am satisfied. Keycloak, dex and other IDP's made me dissatisfied in some steps. As a developer I just dont like the container image taging, please use semver so I can pin major/minor versions.

Suppose you're reading `(next)`, which indicates the upcoming #feature #version of a #software project. The last version was 0.12.0 — what would you expect the next version to be?

We are talking about Semantic Versioning: https://semver.org/ #semver #versioning

https://pridever.org/ Pride Versioning

https://github.com/romversioning/romver Romantic Versioning

https://semver.org/ Semantic Versioning