Selfhosted

40329 readers

485 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

122

immich update has breaking changes (github.com)

submitted 9 months ago by GravitySpoiled@lemmy.ml to c/selfhosted@lemmy.world

39 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] atx_aquarian@lemmy.world 39 points 9 months ago (2 children)

Hot take? This should have been a major version update.

https://semver.org/

[–] ShortN0te@lemmy.ml 33 points 9 months ago (1 children)

Disclaimer ⚠️ The project is under very active development. ⚠️ Expect bugs and breaking changes. ⚠️ Do not use the app as the only way to store your photos and videos. ⚠️ Always follow 3-2-1 backup plan for your precious photos and videos!

Yes project does not follow semantic versioning. But you can consider it it the 0.y.z state where it is even in the semantic versioning allowed to have breaking changes without major version increase.

[–] azertyfun@sh.itjust.works 12 points 9 months ago (2 children)

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver.

I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they're worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.

[–] ShortN0te@lemmy.ml 4 points 9 months ago

Absolutely agree with you. Just because the Versioning looks like x.y.z does not mean it follows that convention. The most prominent example is probably the Linux Kernel Versioning.

Read the notes of the dev team and subscribe to the changelog or update channel.

[–] BlueBockser@programming.dev 3 points 9 months ago

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver

Depending on how one defines the "initial development" phase, those projects are actually conforming to semver spec:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

[–] Sibbo@sopuli.xyz 9 points 9 months ago

Yep. Semver is so much more useful than the marketing versioning which many projects do.