Commit f1b5bb72 authored by Ken Hawkins's avatar Ken Hawkins
Browse files

Component release 20210609-01

Also fixes a few display issues in the component library
parent bfcdf29b
Pipeline #163639 canceled with stages
in 36 minutes and 4 seconds
......@@ -35,13 +35,13 @@ 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 20210531-01`
1. add a tag"
- commit message in a format of: `Component release 20210609-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.1 -m 'Release of precompiled CSS, JS, assets'`
- add a semantic versioned tag `git tag -a v2.5.0-beta.2 -m 'Release of precompiled CSS, JS, assets'`
- Why like this?
- We do not add tags per individual component version, Lerna needs a named tag to see what has changed. This way we get one tag per release "bundle" avoiding tag spamming in the release history.
- Trigger a deploy to the CDN (i.e. `v2.4.5-rc.1`) https://assets.emblstatic.net/vf/v2.4.10/css/styles.css
- 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
1. push the tag
- `git push origin --tags`
1. add release notes to the tag and link to the new blog post
......
{
"version": "2.0.3",
"version": "2.1.0",
"name": "@visual-framework/ebi-header-footer",
"description": "ebi-header-footer component",
"homepage": "https://stable.visual-framework.dev",
......
{
"version": "1.0.6",
"version": "1.0.7",
"name": "@visual-framework/ebi-vf1-integration",
"description": "Compatiblity with legacy EBI Visual Framework 1.x",
"homepage": "",
......
{
"version": "1.0.2",
"version": "1.1.0",
"name": "@visual-framework/embl-notifications",
"description": "embl-notifications component",
"homepage": "https://stable.visual-framework.dev",
......
{
"version": "1.0.0-alpha.1",
"version": "1.0.0-alpha.2",
"name": "@visual-framework/vf-back-to-top",
"description": "vf-back-to-top component",
"homepage": "",
......
{
"version": "1.0.0-alpha.0",
"version": "1.0.0-alpha.1",
"name": "@visual-framework/vf-banner-elixir",
"description": "vf-banner-elixir component",
"homepage": "",
......
{
"version": "1.8.0",
"version": "1.9.0",
"name": "@visual-framework/vf-banner",
"description": "vf-banner component",
"homepage": "https://stable.visual-framework.dev/",
......
{
"version": "2.5.6",
"version": "2.5.7",
"name": "@visual-framework/vf-card",
"description": "vf-card component",
"homepage": "https://stable.visual-framework.dev",
......
{
"version": "1.4.1",
"version": "1.4.2",
"name": "@visual-framework/vf-componenet-rollup",
"description": "vf-componenet-rollup component",
"homepage": "https://stable.visual-framework.dev",
......
{
"version": "1.5.5",
"version": "1.5.6",
"name": "@visual-framework/vf-content",
"description": "vf-content component",
"homepage": "https://stable.visual-framework.dev/",
......
{
"version": "1.1.1",
"version": "1.2.0",
"name": "@visual-framework/vf-details",
"description": "vf-details component",
"homepage": "",
......
{
"version": "1.0.0-alpha.1",
"version": "1.0.0-alpha.2",
"name": "@visual-framework/vf-flag",
"description": "vf-flag component",
"homepage": "",
......
{
"version": "1.4.7",
"version": "1.5.0",
"name": "@visual-framework/vf-intro",
"description": "vf-intro component",
"homepage": "https://stable.visual-framework.dev/",
......
{
"version": "1.5.0",
"version": "1.5.1",
"name": "@visual-framework/vf-section-header",
"description": "vf-section-header component",
"homepage": "https://stable.visual-framework.dev/",
......
{
"name": "@visual-framework/vf-component-generator",
"version": "1.1.4",
"version": "1.1.5",
"description": "Make the config for Visual Framework component interactively.",
"main": "index.js",
"scripts": {
......
{
"name": "@visual-framework/vf-component-library",
"version": "1.1.7",
"version": "1.1.8",
"description": "Generate a static-html site of Visual Framework 2.0 components and docs.",
"main": "index.js",
"scripts": {
......@@ -26,7 +26,7 @@
"dependencies": {
"@11ty/eleventy": "0.12.1",
"@visual-framework/vf-config": "1.0.1-alpha.0",
"@visual-framework/vf-core": "^2.2.26",
"@visual-framework/vf-core": "^2.2.27",
"@visual-framework/vf-extensions": "1.0.0-rc.1",
"html-minifier": "4.0.0",
"node-html-parser": "3.3.4",
......
......@@ -12,11 +12,11 @@ module.exports = {
buildTime: DateTime.fromISO(new Date().toISOString()),
// vfVersion: global.vfVersion,
// use this when NOT tagging a release
vfVersion: "develop",
vfVersionPrefix: "dev.",
// vfVersion: "develop",
// vfVersionPrefix: "dev.",
// use this when tagging a release
// vfVersion: "v2.4.15",
// vfVersionPrefix: "",
vfVersion: "v2.5.0-beta.2",
vfVersionPrefix: "",
sections: {
about: {
url: "/about",
......
......@@ -136,7 +136,7 @@
{%- endif %}
{# Render sub nav for sections #}
{% if section %}
{% if section and (hideSectionNavigation != true) %}
{%- set navigationList = [] -%}
{%- for entry in collections[section] %}
{%- if entry.data.layout %}
......
......@@ -3,7 +3,7 @@ title: Local components
date: 2019-04-09 12:24:50
tags: posts
layout: layouts/components.njk
section: components
section: building
templateEngineOverride: njk, md
pagination:
data: fractalEnvironment.localComponents
......
......@@ -6,9 +6,10 @@ title: Design kit
subtitle: Use Figma software to design and collaborate on ideas without using code.
intro: Here you'll learn about how to use the Figma library, where it is and how to stay posted on updates.
date: 2020-12-14 18:24:50
section: designkit
section: building
order: 5
tags:
- building
- designkit
- sections
layout: layouts/section.njk
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment