RELEASE NOTES - v2.0.0-alpha.6

[khawkins98]

🚨These are draft release notes 🚨

---

We continue to work towards stabilising vf-core for beta.1.

alpha.6 brings a number of architectural improvements that increase the re-usability of vf-core as an npm install, this alpha also brings a number of optimisation and bug fixes.

🔰 What is the VF 2.0? A modular, compatible framework for life science websites and services. Need to know more? Read this

In general there are three major sets of change in alpha.6:

⚙️ vf-core tooling

• npm-installed component assets are placed in the right place #386
• gulpfile optimised to be namespaced (gulp dev is now gulp vf-dev) #396
• builds of static files are now "cleaner" #401
• Refactor of vf-design-tokens #398

🧪 Testing

• Visual regression testing with BackStopJS #376

🎁 BONUS

• vf-eleventy With the improved modularity of vf-core as an npm install, the vf-eleventy starter package is taking shape nicely, which allows for direct use of vf-core patterns and efficient css+js builds https://github.com/visual-framework/vf-eleventy
  • ☝️This is being used for the new vf-welcome site: https://visual-framework.github.io/vf-welcome/

🏗 Components

• Continues tweaks to the vf-masthead architecture #382
• package.json now include most files by default, avoiding issues around missing component files
• npm dependencies of VF components were optimised #387
• Allow vf_lede_text to be set in vf-intro #390
• Fix: vf-form__core references sass files from other components #397
• Typo of class name fixed in vf-link-list #402
• Couple of fixes to vf-content sizing #404
• Increase specificity of utility classes #403

🥙All the things

You can see an overview of all changes from alpha.4 to alpha.5

📢🆕 Preperation for beta.1 The core architecture of the VF component system has been settled for several months and we're working towards our first beta of the Visual Framework so we can:

• communication the VF use case
• trim out-of-scrope features from vf-core
• begin to use vf-core as a dependency in other design systems (such as EMBL's)
• the beta is not feature complete
• convey the separation between vf-core and component releases (vf-core is the architecture, components are independently versioned)

Expect a beta.1 release in June.

📅 What's next?

• Releases are planned for the last Thursday of each month.
• We're working towards beta.1 in June (see details on the beta above)

---

Release to-do script

1. [x] Finish up outstanding ticket/tasks
2. [x] Do release notes
3. [x] Update vf-core package.json version
4. [x] npm publish vf-core
5. [x] Push to npm (lerna)
   • Frist, test the command by doing "skip-npm"
     • lerna publish --no-git-tag-version --conventional-commits --no-push --skip-npm
   • If all went well, reset your branch
   • Then publish to npm
     • lerna publish --no-git-tag-version --conventional-commits --no-push
   • You'll probably have lost your local git changes, so:
     • reset your branch
     • lerna publish --no-git-tag-version --conventional-commits --no-push --skip-npm
     • verify no tags added: git tag
     • push your branch
     • PR version changes
6. [x] PR Merge to master
7. [x] Tag release on master

[auto-comment[bot]]

Thank you for raising an issue. We will try and get back to you as soon as possible. Please make sure you have given us as much context as possible.

[sturobson]

[sturobson]

that took some work