Skip to content

Commit

Permalink
v10
Browse files Browse the repository at this point in the history
BREAKING CHANGE:

Read the docs about migration: https://eufemia.dnb.no/uilib/about-the-lib/releases/eufemia/v10-info
  • Loading branch information
tujoworker committed May 31, 2023
1 parent a47934d commit c9d9501
Show file tree
Hide file tree
Showing 3 changed files with 64 additions and 14 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,14 @@ Version numbers are handled automatically by using [semantic-release](https://gi

Make sure to decorate your **commit messages** with either [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) or [simple-commit-message](https://github.com/bahmutov/simple-commit-message):

- `fix: an example fix message`
- `feat: this is a new feature`
- `BREAKING CHANGE (must be in the footer of the commit)`
- `fix: an example fix message` as the subject
- `feat: this is a new feature` as the subject
- `BREAKING CHANGE:` in the footer of the commit, the subject does not really matter. See example below.

If you are working on a single component update, you can use
If you are working on a single component update, you can use a decoration and a scope in parenthesis:

- `fix(ExampleComponent): an example fix message` or
- `feat(ExampleComponent): this is a new feature`.
- `fix(ExampleComponent): an example fix message`
- `feat(ExampleComponent): this is a new feature`

You can also use the following decorators – but keep in mind, they won't be included in the [releases change log](https://github.com/dnbexperience/eufemia/releases):

Expand All @@ -35,6 +35,26 @@ You can also use the following decorators – but keep in mind, they won't be in
- `perf:`
- `test:`

Example of a breaking change commit message:

```text
commit subject with optional decorator
Body with text
Several lines
BREAKING CHANGE:
Subject (will be a list item):
Markdown text over several lines.
Additional text such as:
1. List item
2. List item
```

### Ignore CI run

You can either include `[skip ci]` in your [commit message](https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/) or let your branch name end with `--skip-ci`.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,12 +1,17 @@
---
draft: true
---

# v10

- [Migration](#migration)
- [Changes](#changes)
- [Feature](#features)
- [v10](#v10)
- [Migration](#migration)
- [StepIndicator](#stepindicator)
- [Table](#table)
- [Slider](#slider)
- [Timeline](#timeline)
- [Anchor](#anchor)
- [Tooltip](#tooltip)
- [Icon](#icon)
- [Lists](#lists)
- [Deprecations](#deprecations)
- [Install](#install)

## Migration

Expand Down Expand Up @@ -79,4 +84,4 @@ $ npm i @dnb/eufemia@10
$ yarn add @dnb/eufemia@10
```

_June, 1. 2022_
_December, 24. 2022_
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
draft: true
---

# v11

- [v11](#v11)
- [Migration](#migration)
- [Install](#install)

## Migration

v11 of @dnb/eufemia contains _breaking changes_. As a migration process, you can simply search and replace:

## Install

To upgrade to @dnb/eufemia v11 with NPM, use:

```bash
$ npm i @dnb/eufemia@11
# or
$ yarn add @dnb/eufemia@11
```

_June, 1. 2023_

0 comments on commit c9d9501

Please sign in to comment.