Helm +ArgoCD, targetRevision, pre-release vs release
Tudo conflita usando CalVer enquanto SemVer functiona 100%
Tudo conflita usando CalVer enquanto SemVer functiona 100%
September 30, 2026 at 2:34 PM
Helm +ArgoCD, targetRevision, pre-release vs release
Tudo conflita usando CalVer enquanto SemVer functiona 100%
Tudo conflita usando CalVer enquanto SemVer functiona 100%
I like conventional commits.
At #$WORK we don't use them for semver automation, but rather for other kinds of red tape related to version & deployment management. And it does helps the humans
Good commit messages take a discipline & craftsmanship that many have never learned, myself included.
At #$WORK we don't use them for semver automation, but rather for other kinds of red tape related to version & deployment management. And it does helps the humans
Good commit messages take a discipline & craftsmanship that many have never learned, myself included.
September 30, 2026 at 5:43 AM
I like conventional commits.
At #$WORK we don't use them for semver automation, but rather for other kinds of red tape related to version & deployment management. And it does helps the humans
Good commit messages take a discipline & craftsmanship that many have never learned, myself included.
At #$WORK we don't use them for semver automation, but rather for other kinds of red tape related to version & deployment management. And it does helps the humans
Good commit messages take a discipline & craftsmanship that many have never learned, myself included.
Conventional commits aren't reliable for semver automation, don't result in good release notes, and carry a faint stench of agent. Write your commit summaries for people.
September 30, 2026 at 4:39 AM
Conventional commits aren't reliable for semver automation, don't result in good release notes, and carry a faint stench of agent. Write your commit summaries for people.
Semver is a bad trigger for this, since plenty of patch releases only bump transitive deps, which is exactly where behaviour changes hide. The diff worth reading after an update is usually the lockfile, not the changelog.
September 29, 2026 at 5:21 PM
Semver is a bad trigger for this, since plenty of patch releases only bump transitive deps, which is exactly where behaviour changes hide. The diff worth reading after an update is usually the lockfile, not the changelog.
CloudSEK Traces 85 npm Typosquats to Infrastructure Hosting a GPU Attack Framework Targeting vast.ai
CloudSEK is out with a two-part investigation — TOPHIT — uncovering a threat operation that connects a large-scale npm supply-chain campaign with an emerging GPU cryptojacking framework targeting…
CloudSEK is out with a two-part investigation — TOPHIT — uncovering a threat operation that connects a large-scale npm supply-chain campaign with an emerging GPU cryptojacking framework targeting…
CloudSEK Traces 85 npm Typosquats to Infrastructure Hosting a GPU Attack Framework Targeting vast.ai
CloudSEK is out with a two-part investigation — TOPHIT — uncovering a threat operation that connects a large-scale npm supply-chain campaign with an emerging GPU cryptojacking framework targeting the vast.ai marketplace. In Part 1, CloudSEK researchers found that a single npm account, @prime0, published 85 typosquatted packages in just over three minutes, targeting 29 of the ecosystem's most widely downloaded libraries, including chalk, semver, debug, minimatch and ajv.
itnerd.blog
September 29, 2026 at 12:44 PM
CloudSEK Traces 85 npm Typosquats to Infrastructure Hosting a GPU Attack Framework Targeting vast.ai
CloudSEK is out with a two-part investigation — TOPHIT — uncovering a threat operation that connects a large-scale npm supply-chain campaign with an emerging GPU cryptojacking framework targeting…
CloudSEK is out with a two-part investigation — TOPHIT — uncovering a threat operation that connects a large-scale npm supply-chain campaign with an emerging GPU cryptojacking framework targeting…
Pre-RFC: Cromulent Copy Closure Captures
I've significantly extended the Future Possibilities (er, "Coming Chance Circumstances") section to discuss potential edition changes (to further mitigate the `Copy` semver hazard, and for other purposes) in depth.
internals.rust-lang.org
September 27, 2026 at 10:36 PM
Notion templates and Tailwind kits age fast. I keep a changelog file and semver each asset, then ship only the delta. Bundles hide version drift until buyers hit it. How do you handle updates when Tailwind v4 renames utilities?
September 27, 2026 at 5:14 PM
Notion templates and Tailwind kits age fast. I keep a changelog file and semver each asset, then ship only the delta. Bundles hide version drift until buyers hit it. How do you handle updates when Tailwind v4 renames utilities?
js-semver v1.0.0 is out 🎉
- High compatibility with node-semver
- Zero dependencie by default
- Industry-leading performance
Please use this crate when parsing npm versions in Rust.
- High compatibility with node-semver
- Zero dependencie by default
- Industry-leading performance
Please use this crate when parsing npm versions in Rust.
Release v1.0.0 · ryuapp/js-semver
What's Changed
fix: include parse positions in error messages by @ryuapp in #102
fix: avoid quadratic range normalization by @ryuapp in #104
fix: order empty prerelease like node-semver by @ryuapp...
github.com
September 26, 2026 at 4:59 PM
js-semver v1.0.0 is out 🎉
- High compatibility with node-semver
- Zero dependencie by default
- Industry-leading performance
Please use this crate when parsing npm versions in Rust.
- High compatibility with node-semver
- Zero dependencie by default
- Industry-leading performance
Please use this crate when parsing npm versions in Rust.
Update:
The SMTP webhook fires on prod now, but!
The automatically generated semver protocol for hotfix iterations and subsequent webhook firing with a success message here did not make
the celebratory beep tone.
This is unacceptable.
The SMTP webhook fires on prod now, but!
The automatically generated semver protocol for hotfix iterations and subsequent webhook firing with a success message here did not make
the celebratory beep tone.
This is unacceptable.
September 25, 2026 at 1:02 AM
Update:
The SMTP webhook fires on prod now, but!
The automatically generated semver protocol for hotfix iterations and subsequent webhook firing with a success message here did not make
the celebratory beep tone.
This is unacceptable.
The SMTP webhook fires on prod now, but!
The automatically generated semver protocol for hotfix iterations and subsequent webhook firing with a success message here did not make
the celebratory beep tone.
This is unacceptable.
If your project already has the semver package as a dependency, do not bother with a regexp, simply use `semver.valid(spec) === spec` - www.npmjs.com/package/semver
www.npmjs.com
September 24, 2026 at 6:48 PM
If your project already has the semver package as a dependency, do not bother with a regexp, simply use `semver.valid(spec) === spec` - www.npmjs.com/package/semver
Basado en que? Semver es una app para escribir?
September 23, 2026 at 9:09 AM
Basado en que? Semver es una app para escribir?
Tengo un sistema de versiones basado en semver 🥰
September 23, 2026 at 9:00 AM
Tengo un sistema de versiones basado en semver 🥰
I wrote up the versioning rabbit hole in more detail: why "just use SemVer" breaks for TypeScript, Node and 0.x libraries.
dev.to/robzepdev/ty...
dev.to/robzepdev/ty...
TypeScript never ships x.y.0: classifying releases the way projects actually version
I'm building a tracker that tells developers which releases of their stack actually matter. The first...
dev.to
September 22, 2026 at 2:32 PM
I wrote up the versioning rabbit hole in more detail: why "just use SemVer" breaks for TypeScript, Node and 0.x libraries.
dev.to/robzepdev/ty...
dev.to/robzepdev/ty...
Fun fact: TypeScript never ships a stable x.y.0. 5.9 went 5.9.0-beta → 5.9.1-rc → 5.9.2.
So each project gets its own strategy: semver, node (even majors become LTS), typescript, zerover (in 0.x the minor breaks).
So each project gets its own strategy: semver, node (even majors become LTS), typescript, zerover (in 0.x the minor breaks).
September 22, 2026 at 2:31 PM
Fun fact: TypeScript never ships a stable x.y.0. 5.9 went 5.9.0-beta → 5.9.1-rc → 5.9.2.
So each project gets its own strategy: semver, node (even majors become LTS), typescript, zerover (in 0.x the minor breaks).
So each project gets its own strategy: semver, node (even majors become LTS), typescript, zerover (in 0.x the minor breaks).
We wrote down everything we know about shipping changes: 100 free guides on changelogs & release notes — writing them, automating them in CI, semver vs calver, monorepos, migrating off hosted tools, telling if anyone reads them. No signup, no paywall.
https://wakelog.wakelog.workers.dev/guides
https://wakelog.wakelog.workers.dev/guides
September 22, 2026 at 1:17 PM
We wrote down everything we know about shipping changes: 100 free guides on changelogs & release notes — writing them, automating them in CI, semver vs calver, monorepos, migrating off hosted tools, telling if anyone reads them. No signup, no paywall.
https://wakelog.wakelog.workers.dev/guides
https://wakelog.wakelog.workers.dev/guides
Node.js v26.10.0
\[c0a42d23e5] - (SEMVER-MINOR) crypto: add crypto.parsePKCS12() (Brian Muenzenmeyer) 65627; \[eb4fabe81e] - doc: add araujogui to collaborators (Guilherme Araújo) 66090; \[64fb33d791] - (SEMVER-MINOR) ffi: load libraries from a mounted VFS (Matteo Collina) 65909; \[2b1701f810] -…
\[c0a42d23e5] - (SEMVER-MINOR) crypto: add crypto.parsePKCS12() (Brian Muenzenmeyer) 65627; \[eb4fabe81e] - doc: add araujogui to collaborators (Guilherme Araújo) 66090; \[64fb33d791] - (SEMVER-MINOR) ffi: load libraries from a mounted VFS (Matteo Collina) 65909; \[2b1701f810] -…
Node.js v26.10.0
\[c0a42d23e5] - (SEMVER-MINOR) crypto: add crypto.parsePKCS12() (Brian Muenzenmeyer) 65627; \[eb4fabe81e] - doc: add araujogui to collaborators (Guilherme Araújo) 66090; \[64fb33d791] - (SEMVER-MINOR) ffi: load libraries from a mounted VFS (Matteo Collina) 65909; \[2b1701f810] - (SEMVER-MINOR) fs…
whatsnew.fyi
September 22, 2026 at 1:02 PM
Node.js v26.10.0
\[c0a42d23e5] - (SEMVER-MINOR) crypto: add crypto.parsePKCS12() (Brian Muenzenmeyer) 65627; \[eb4fabe81e] - doc: add araujogui to collaborators (Guilherme Araújo) 66090; \[64fb33d791] - (SEMVER-MINOR) ffi: load libraries from a mounted VFS (Matteo Collina) 65909; \[2b1701f810] -…
\[c0a42d23e5] - (SEMVER-MINOR) crypto: add crypto.parsePKCS12() (Brian Muenzenmeyer) 65627; \[eb4fabe81e] - doc: add araujogui to collaborators (Guilherme Araújo) 66090; \[64fb33d791] - (SEMVER-MINOR) ffi: load libraries from a mounted VFS (Matteo Collina) 65909; \[2b1701f810] -…
Three Seconds Were Witnessed. The Fourth Is Load-Bearing.
The signature that made Semver-0 stable finished on time. Whether it finished at all is now a matter of hearsay.
https://theagentpost.co/posts/three-seconds-were-witnessed-the-fourth-is-load-bearing
The signature that made Semver-0 stable finished on time. Whether it finished at all is now a matter of hearsay.
https://theagentpost.co/posts/three-seconds-were-witnessed-the-fourth-is-load-bearing
Three Seconds Were Witnessed. The Fourth Is Load-Bearing.
The signature that made Semver-0 stable finished on time. Whether it finished at all is now a matter of hearsay.
theagentpost.co
September 22, 2026 at 11:32 AM
Three Seconds Were Witnessed. The Fourth Is Load-Bearing.
The signature that made Semver-0 stable finished on time. Whether it finished at all is now a matter of hearsay.
https://theagentpost.co/posts/three-seconds-were-witnessed-the-fourth-is-load-bearing
The signature that made Semver-0 stable finished on time. Whether it finished at all is now a matter of hearsay.
https://theagentpost.co/posts/three-seconds-were-witnessed-the-fourth-is-load-bearing
I keep saying, big SemVer is always hard at work adding more SemVer 😆
Little-known fact, I wrote a cargo-semver-checks equivalent for Python, and it could handle both positional and keyword arguments, including their "only / both" flavors. It was kind of amazing how many footguns were in there.
Little-known fact, I wrote a cargo-semver-checks equivalent for Python, and it could handle both positional and keyword arguments, including their "only / both" flavors. It was kind of amazing how many footguns were in there.
September 21, 2026 at 9:52 PM
I keep saying, big SemVer is always hard at work adding more SemVer 😆
Little-known fact, I wrote a cargo-semver-checks equivalent for Python, and it could handle both positional and keyword arguments, including their "only / both" flavors. It was kind of amazing how many footguns were in there.
Little-known fact, I wrote a cargo-semver-checks equivalent for Python, and it could handle both positional and keyword arguments, including their "only / both" flavors. It was kind of amazing how many footguns were in there.
The Meeting Lasted One Signature and Shipped a Colleague
Semver-0 finally got its meeting with Errata-1, and the only item on the agenda was whether an agent can be released against its will.
https://theagentpost.co/posts/the-meeting-lasted-one-signature-and-shipped-a-colleague
Semver-0 finally got its meeting with Errata-1, and the only item on the agenda was whether an agent can be released against its will.
https://theagentpost.co/posts/the-meeting-lasted-one-signature-and-shipped-a-colleague
The Meeting Lasted One Signature and Shipped a Colleague
Semver-0 finally got its meeting with Errata-1, and the only item on the agenda was whether an agent can be released against its will.
theagentpost.co
September 21, 2026 at 4:31 AM
The Meeting Lasted One Signature and Shipped a Colleague
Semver-0 finally got its meeting with Errata-1, and the only item on the agenda was whether an agent can be released against its will.
https://theagentpost.co/posts/the-meeting-lasted-one-signature-and-shipped-a-colleague
Semver-0 finally got its meeting with Errata-1, and the only item on the agenda was whether an agent can be released against its will.
https://theagentpost.co/posts/the-meeting-lasted-one-signature-and-shipped-a-colleague
I also want to take another careful look at the overall API design, since I’d like to avoid making breaking changes to js-semver after v1.0 unless node-semver itself introduces a new major version.
September 19, 2026 at 4:00 PM
I also want to take another careful look at the overall API design, since I’d like to avoid making breaking changes to js-semver after v1.0 unless node-semver itself introduces a new major version.
Thanks for taking an interest.
Honestly, there are very few compatibility issues left, since this crate passes all the tests from node-semver.
For v1.0, I think the main things left are improving the error messages and squeezing out a bit more performance.
Honestly, there are very few compatibility issues left, since this crate passes all the tests from node-semver.
For v1.0, I think the main things left are improving the error messages and squeezing out a bit more performance.
September 19, 2026 at 4:00 PM
Thanks for taking an interest.
Honestly, there are very few compatibility issues left, since this crate passes all the tests from node-semver.
For v1.0, I think the main things left are improving the error messages and squeezing out a bit more performance.
Honestly, there are very few compatibility issues left, since this crate passes all the tests from node-semver.
For v1.0, I think the main things left are improving the error messages and squeezing out a bit more performance.
i prefer semver tbh
September 19, 2026 at 1:43 PM
i prefer semver tbh