Tag: semantic-versioning

Found 63 results for 'semantic-versioning'.

1) node.js - What's the difference between tilde(~) and caret(^) in package.json?
2) java - Should it be considered a BC break to return clone instead of new self?
3) semantic-versioning - Should I treat additional linter restrictions as breaking backwards compatibility?
4) node.js - What's the difference between tilde(~) and caret(^) in package.json?
5) version-control - Multiple git repositories with a common core lib
6) architecture - Best practices on sharing code between open source libraries
7) versioning - Semantic versioning with bugfixes and new features in the same release
8) node.js - What's the difference between tilde(~) and caret(^) in package.json?
9) node.js - What's the difference between tilde(~) and caret(^) in package.json?
10) interfaces - Major or Minor Revision Change when Implementing an Interface
11) versioning - How to Name Different Branches with Identical Functionality in Semantic Versioning
12) versioning - Semantic versioning for content websites
13) versioning - Semantic Versioning and splitting apart a library, providing a bundled build
14) testing - Update semver minor version on test updates?
15) git - Using Gitflow and Semantic Versioning: How to avoid version number conflicts when merging?
16) api - Why do we must declare a public API when using semantic versionning?
17) version-control - Git, semantic versioning and how it fits into (my) a typical development timeline?
18) c# - How to use Git Flow with multiple dependent projects
19) github - GitHub Versioning - Organizing Structure
20) versioning - When and how to do a release?
21) versioning - Why are minor versions of dependencies pinned, despite possibly having bugs?
22) versioning - Is fast major version bumping an evidence of poor design?
23) semantic-versioning - Does doc comments count as declaring a public API?
24) semantic-versioning - Removing old (semantically versioned) NuGet packages
25) continuous-integration - Why is build.number an "abuse" of semantic versioning?
26) testing - Testing that a library is backwards compatible
27) versioning - Version number for multiple softwares coming from same code base
28) versioning - Semantic versioning when fixing an important bug
29) .net - In the context of semantic versioning, does a change in the default configuration warrant a new major version?
30) semantic-versioning - Is adding support for another operation system a minor version or a patch?
31) semantic-versioning - How do deal with bugs in semantic versioning introduced in old branches
32) c++ - Does changing the name of a namespace count as a MAJOR change in semantic versioning?
33) versioning - Major version number as part of package name / namespace?
34) design - GitFlow, should my release branch include minor version number?
35) versioning - When to increment build number?
36) web-development - HTTP API Versioning and Need to Introduce Breaking Changes to All Supported Versions
37) database - Projects version and database compatibility
38) versioning - How is a reproducible build guaranteed with version ranges in NPM?
39) versioning - Does Semantic Versioning allow 4 components in version numbers?
40) versioning - Does Implementing a New Function Imply A New Major Version?
41) development-process - Which SemVer version to use between releases?
42) version-control - How to version when using trunk based development
43) semantic-versioning - Can a library reach v1.0 when its dependencies haven't?
44) versioning - What Semantic Version increment to use for a configuration file alteration?
45) versioning - How to treat bugs that users thought were a feature?
46) version-control - Is it appropriate to convert a project to a different language and keep the same versioning?
47) node.js - Change semver versioning after dropping node eninge versions
48) enum - Semantic Versioning in OpenAPI with string "enum": new values OK?
49) python - Using semantic version with trunk based development for Python package
50) libraries - Semantic Version Change (to application) when Upgrading Libraries Involved