semantic-versioning

semantic-versioning

Automate semver in ConcourseCI

How can I combine semantic versions?

How to introduce incompatible changes while remaining in major version zero?

Semantic versioning - major version for a traditional web application

semver: matching a pre-release suffix (3.* =/= 3.4.5-1)

Breaking change in previous major release

Concourse: Use a semver resource to control which artifact to use from s3

releasing alpha to beta to production with SemVer

What is the next Minor release after 0.7.9?

Versioning multiple configurations

how to get top 5 semantic versions if you are using Semantic Versioning in a folder

Reason for MINOR vs PATCH rules in SemVer

When using semver when to upgrade/bump to 1.0.0 (stable)

Under what version is semantic versioning versioned?

What exactly is considered a breaking change to a PureScript library?

What is the breaking change in semver 2.0.0

What does version.x mean?

GitVersion – selective versioning multiple assemblies of the same project

When to increase minor version with SEMVER?

How to use gitversion on older codebase

Is 0.0.1 valid semver?

Semver: Can a function be removed without a major version bump?

Semantic versioning : Incrementing by two

Does adding a parameter to a function definition require a new major version?

Would a protocol's version need a “patch”?

Is there an equivalent scheme to Semantic Versioning for non-API software?

What does “public api” means in Semantic Versioning?

page:1 of 1 main page

Categories

stm32f4discovery

latitude-longitude

apache-kafka-connect

advanced-custom-fields

firebase-storage

google-search-console

kubernetes-go-client

jquery-ui-accordion

numerical-methods

google-maps-ios

system.net.mail

jquery.repeater

amazon-appstore

android-augmented-reality

csrf-protection

targetinvocationexception

flash-media-server

pointer-to-array

nhibernate-queryover

window-decoration

html-components

Resources