search

decanTyme / chartjs-plugin-tailwindcss-colors

Use TailwindCSS to colorize your Chart.js components!
https://www.npmjs.com/package/chartjs-plugin-tailwindcss-colors
MIT License
3 stars 0 forks source link

[BETA] Initial Spec #8

Closed decanTyme closed 1 year ago

decanTyme commented 1 year ago

Main features should be good (and ready) enough to be on the beta distribution channel, as far as I'm aware of. Any further updates and optimizations will go to alpha for now. As always, please do post an issue if there are bugs encountered!

Also, Chart.js v4 has just been released. It won't be guaranteed for now, but in my initial testing using it on my projects, it still works as expected. Will have the updates and fixes pushed on alpha channel first as I test things out further.

Closed, see comment below.

decanTyme commented 1 year ago

Currently investigating a way to just use major version 0. This would completely reset releases (and possibly a complete rebase too). This is preferred because as the project continues as a "work in progress" for many commits to come, pushing to alpha per semantic-release config will result in main being woefully stale. It also doesn't make much sense as initial releases rather than v0, and it should be reserved for experimental changes on stable versions. Thankfully, nothing significant has been pushed (and released) to main yet, and only alpha versions have been released, which should be fine considering it's in alpha and implies that things may break.

As said before, semantic-release does not support this officially. Apparently, the SemVer specs itself is ambiguous (or rather missing, at least on what to do with bumps) on versions < 1.0.0. This, in turn, makes decisions for releases on major version 0 preferential. This is why the difference in 0.y.z bumps between semantic-release and standard-version exists.

While I kinda agree with the standard-version point of view on this, in this particular case semantic-release should be alright. If I do end up deciding to reset releases, ~these changes will be merged to main~ the alpha branch will be renamed as main instead and changes will be released as 0.x and not on beta as previously intended. Alpha versions will then be unpublished after a while, ~though breaking experimental changes will still be pushed to pre-release branches before merging to main as a way to preserve standard-version behavior~ as versioning post-rebase will closely follow npm semver rules on ^0.y.z. ~Fixes and non-breaking~ All changes will be pushed directly to main.

Closing this for now.