@@ -35,10 +35,10 @@ A reference guide on how to do releases of the VF [monorepo](https://www.toptal.
### 4. Post-release
1. commit and push changes to the `develop` branch
- commit message in a format of: `Component release 20210609-01`
- commit message in a format of: `Component release 20210705-01`
1. add a tag
- see last tag `git describe --abbrev=0 --tags`
- add a semantic versioned tag `git tag -a v2.5.0-beta.2 -m 'Release of precompiled CSS, JS, assets'`
- add a semantic versioned tag `git tag -a v2.5.0-beta.5 -m 'Release of precompiled CSS, JS, assets'`
- Why like this?
- We do not add tags per individual component version. However, Lerna needs a named tag to see what has changed. With our method we get one tag per release bundle and avoid tag spamming in the release history.
- Trigger a deploy to the CDN (i.e. `v2.5.0`) https://assets.emblstatic.net/vf/v2.4.10/css/styles.css
subtitle: Beta 5 focused on more fully integrating typography design tokens as we create a more visually and technically consistent 2.5.0 rollup release.
date: 2021-07-05 15:20:29
version: 2.5.0-beta.5
tags:
- posts
- changelog
layout: layouts/post.njk
---
{% markdown %}
The usage of [design token information](/design-tokens) has been improved with many components now fully using the token for typography colours. Additionally, we have improved the accessibility of the main text colour to be an off-black. Previously it was an [over-contrasted solid `#000` black](https://github.com/visual-framework/vf-core/issues/1587#issuecomment-866668118).
We've also made small fixes and documentation improvements to `vf-hero`, the ELIXIR banner and the `vf-profile`.
For our next beta we aim to continue documentation polish and some [foundational work on navigation patterns](https://github.com/visual-framework/vf-core/discussions/1299) during a sprint the week of 19 July. With those done we hope to release rollup 2.5.0 by mid-August.
As a reminder, the rollup CSS and JS are compilations of many independently versioned components and is likely to contain changes that may disrupt the look of your site. We advise testing. Even better is to build your own CSS rollup from the npm sources, [you can find a guide here]({{ '/building' | url }}).
{#- don't forget to add the latest version to /tools/vf-component-library/src/site/_data/siteConfig.js -#}
* Updates the default hero spacing to be equivalent to 1200 (was: 800). This better matches the actual default usage in practice and is based off design feedback for consistency.
* Hides 1600 variant that has gone unused.
* Readme updated to note that most uses will want a background image at 3000 by 1000 pixels.
