bootstrap-vue-next VS semver

There's this project: https://github.com/bootstrap-vue/bootstrap-vue-next . But considering low number of dynamic components in Bootstrap, it is pretty easy to build a wrapper only for them yourself, and use other elements as simple HTML.

Moving over to typescript and vue 2.7 has been great, and we are making progress on refactoring our components to the composition API. But if by next summer there is no suitable replacement to bootstrap-vue ready, then there will be a lot of pain. I realize the maintainer of bootstrap-vue is in Ukraine so my hope is that this project can make it in time.

But it misses some really basic things. Like a carousel for example. So in the end, I got sidetracked making a PR for it: https://github.com/cdmoro/bootstrap-vue-3/pull/691

https://github.com/cdmoro/bootstrap-vue-3 wonder if anyone tried this guy’s version yet

Somebody already ported bootstrap vue here https://github.com/cdmoro/bootstrap-vue-3. not going to lie but your implementation seems like just a wrapper which people do not want html/css abstracted if they don't have extra functionality. I'd rather use my own components which literally take a few minutes to write and you can specify whatever you want in there instead of being restricted by using your library. Just seems like a headache to me when there is a bug or I need to expand on the feature, sorry just my honest feedback. Maybe the library could just be base components that people can copy paste?

I found a forked alternative that looks promising (https://github.com/cdmoro/bootstrap-vue-3)

We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.

We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org