Semantic Versioning and splitting apart a library, providing a bundled build

Posted by Derick Bailey on Programmers See other posts from Programmers or by Derick Bailey
Published on 2013-08-14T14:03:09Z Indexed on 2013/10/22 10:14 UTC
Read the original article Hit count: 295

Filed under:

versioning

|

semantic-versioning

I've got a nice, fairly popular JavaScript library that is following Semantic Versioning.

The current library has a few dependency libraries, which are available either as separate downloads or as part of a single bundled download. I see a need to head down this path further. I want to extract additional, smaller libraries out of the one larger library. Each of these extracted libraries would be available as separate files, or inside of the one bundled build, again.

If I go down this path of extracting the libraries, and providing a bundled version of the final code, does this require a full version change in semantic versioning? Would I have to bump from 1.x to 2.x?

My first thought it no: I will not change any public API, so I don't have to change the major version number. But then I wonder... well, I am restructuring a lot of things, even though the final API for the bundled version would be the same.

Is there a clear answer from semver on something like this? Do I need to bump first, second or third dot? Or something else?

© Programmers or respective owner

Related posts about versioning

Web Site Performance and Assembly Versioning – Part 3 Versioning Combined Files Using Mercurial

as seen on ASP.net Weblogs - Search for 'ASP.net Weblogs'
Minification and Concatination of JavaScript and CSS Files Versioning Combined Files Using Subversion Versioning Combined Files Using Mercurial – this post I have worked on a project recently where there was a need to version the system (library dll, css and javascript files) by date and… >>> More
Web Site Performance and Assembly Versioning – Part 2 Versioning Combined Files Using Subversion

as seen on ASP.net Weblogs - Search for 'ASP.net Weblogs'
Ok so it took a while to post this second part. Many apologies, we had a big roll out of a new platform at work and many things had to get sidelined. So this is the second part in a short series of website performance and using versioning to help improve it. Minification and Concatination of JavaScript… >>> More
Sharepoint webpart-page versioning

as seen on Stack Overflow - Search for 'Stack Overflow'
On webpart-pages it is possible modify the contained webparts over the Web by using Site Actions-Edit page. Is there a possibility to view the version history of such a page? >>> More
jboss envers for versioning?

as seen on Stack Overflow - Search for 'Stack Overflow'
I have entities that required versioning support and from time to time, i will need to retrieve old version of the entity . should i just use options available 1. http://stackoverflow.com/questions/762405/database-data-versioning 2. jboss envers (can this be used on any web server,tomcat,jetty… >>> More
UPK Content State

as seen on Oracle Blogs - Search for 'Oracle Blogs'
State is an editable property for communicating the status of a document in the UPK library. This is particularly helpful when working with other authors in a development team. Authors can assign a state to any document using the values that are defined in the master list. The default master list… >>> More

Related posts about semantic-versioning

Semantic Versioning and splitting apart a library, providing a bundled build

as seen on Programmers - Search for 'Programmers'
I've got a nice, fairly popular JavaScript library that is following Semantic Versioning. The current library has a few dependency libraries, which are available either as separate downloads or as part of a single bundled download. I see a need to head down this path further. I want to extract additional… >>> More
Using <= for every dependency in case of following semantic versioning idea

as seen on Programmers - Search for 'Programmers'
As Semantic Versioning (and common sense) declares - the major version is incremented in case if non backward compatible change is introduced. Now let's assume we have a project called Project that has a current version 1.0.42 and a library Lib it depends on that is of a 2.1.3 version at the moment… >>> More
In the context of semantic versioning, does a change in the default configuration warrant a new major version?

as seen on Programmers - Search for 'Programmers'
My module is enabled by default (i.e. when you add the module). There's also a configuration you can optionally use, which supports an enabled="true|false" setting. This way the module can be disabled after it's been added, without the need to remove the module. But I realized the module doesn't… >>> More
UppercuT v1.0 and 1.1–Linux (Mono), Multi-targeting, SemVer, Nitriq and Obfuscation, oh my!

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Recently UppercuT (UC) quietly released version 1 (in August). I’m pretty happy with where we are, although I think it’s a few months later than I originally planned. I’m glad I held it back, it gave me some more time to think about some things a little more and also the opportunity to receive a patch… >>> More
Strategy for versioning on a public repo

as seen on Programmers - Search for 'Programmers'
Suppose I'm developing a (javascript) library which is hosted on a public repo (e.g. github). My aim in terms of how version numbers are assigned and incremented is to follow the guidelines of semantic versioning. Now, there's a number of files in my project which compose the actual lib and a number… >>> More