mirror of https://github.com/nocodb/nocodb
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
41 lines
1.8 KiB
41 lines
1.8 KiB
3 years ago
|
---
|
||
|
|
title: "Making a release"
|
||
|
|
description: "Making a release"
|
||
|
|
position: 2000
|
||
|
|
category: "Engineering"
|
||
|
|
menuTitle: "Making a release"
|
||
|
|
---
|
||
|
|
|
||
|
|
> This is exclusive to NocoDB team members only
|
||
|
|
|
||
|
|
## 1. Merge ```develop``` to ```master```
|
||
|
|
- When several features are included in develop branch and they are ready to be released, make a PR from `develop` branch to `master` branch. At least one NocoDB team member approval is required.
|
||
|
|
|
||
|
|
## 2. Publish frontend
|
||
|
|
- Navigate to `packages/nc-gui` and execute following command.
|
||
|
|
```bash
|
||
|
|
npm run build:copy:jsdeliver
|
||
|
|
```
|
||
|
|
## 3. Install frontend
|
||
|
|
- Install the latest published version of `nc-lib-gui` in `packages/nocodb`, package version can be extracted from result of step 1 or copy it from `packages/nc-lib-gui/package.json`. While installing, add `-E` to install exact version of the package.
|
||
|
|
|
||
|
|
- Example: for latest published version `0.84.8`
|
||
|
|
```bash
|
||
|
|
npm i -E nc-lib-gui@0.84.8
|
||
|
|
```
|
||
|
|
|
||
|
|
## 4. Publish backend
|
||
|
|
- Bump package version in `packages/nocodb/package.json` file.
|
||
|
|
- Publish the npm package by running following npm command in `packages/nocodb` folder.
|
||
|
|
```
|
||
|
|
npm run obfuscate:build:publish
|
||
|
|
```
|
||
|
|
|
||
|
|
## 5. Prepare release notes
|
||
|
|
- Populate release note by running following github action (on `master` branch) - `Release : Draft Notes`. While running the action you have to provide 2 inputs:
|
||
|
|
- **Tag** : Provide current package version
|
||
|
|
- **Previous Tag** : Provide previously released tag version
|
||
|
|
|
||
|
|
## 6. Publish docker & release
|
||
|
|
- Publish docker image by running `Release : Docker` action in github (on `master` branch), where you have to provide the package version/tag.
|
||
|
|
- Update the populated release (remove issues which is not related to release) draft and publish. In release note you can use `Auto-generate release notes` button to populate release content from commits & PR.
|