Introduce versioning to the CSS Library
One very important aspect that our CSS library should have is versioning. Our library when released to the public (production).
For that we should do the following:
- Follow the new GNOME's versioning schema: https://discourse.gnome.org/t/new-gnome-versioning-scheme/4235
- Create a Job for the
main
branch that is optional and executes theversioning
script- This job should execute the versioning script (which bumps the NPM package)
- This job should create dedicated artefacts (in a zip file) including the files from the
dist
folder - The
dist
folder should have all the files renamed with the version. Eg.:gnome-websites.css
becomesgnome-websites-vXX.XX.css
- The job should in the end execute the Conventional Changelogs (https://gitlab.gnome.org/Teams/Engagement/websites/gnome-websites-framework/-/issues/43) script.
- The versioned NPM package should be published.
- The published NPM package should ONLY contain the contents of the
dist
folder. We don't want to package the source or docs folder since there's no value in packaging that.
- The published NPM package should ONLY contain the contents of the
Edited by Claudio Wunder