Please check if your PR fulfills the following requirements in this order:
[x] The PR name follows the naming convention release-v[0-9]+.[0-9]+.[0-9].
[x] The brach follows the naming convention release-v[0-9]+.[0-9]+.[0-9].
[x] The CHANGELOG.md is updated with a version header # [<version>](https://github.com/dlr-eoc/ukis-frontend-libraries/tree/v<version>) (<date>) (<description>).
[x] The correct version and tag was set with npm version <major | minor | patch> -m "Version for release XYZ".
[x] All versions are synced with node scripts/library/index.js --set-source.
[x] The main package-lock.json was updated with npm intsall.
[x] The Tag v[0-9]+.[0-9]+.[0-9] was pushed with the branch.
[x] The Project is building without errors see and check if the build job was successful.
[x] Add the Label RELEASE to the PR.
Then a release on GitHub is created and the built packages are published.
Release PR Checklist
For creating a new version see DEVELOPMENT/new version and see Release pull request.
Please check if your PR fulfills the following requirements in this order:
release-v[0-9]+.[0-9]+.[0-9]
.release-v[0-9]+.[0-9]+.[0-9]
.# [<version>](https://github.com/dlr-eoc/ukis-frontend-libraries/tree/v<version>) (<date>) (<description>)
.npm version <major | minor | patch> -m "Version for release XYZ"
.node scripts/library/index.js --set-source
.npm intsall
.RELEASE
to the PR.Then a release on GitHub is created and the built packages are published.
If everything works fine the PR can be merged.