-
Notifications
You must be signed in to change notification settings - Fork 268
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* 4.4.0 * Update README.md * Update upgrade43-44.md * Update readme * lock update Co-authored-by: arditdomi <[email protected]>
- Loading branch information
Showing
29 changed files
with
1,172 additions
and
66 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,89 @@ | ||
--- | ||
Title: Upgrading from ADF v4.2 to v4.3 | ||
--- | ||
|
||
# Upgrading from ADF v4.2 to v4.3 | ||
|
||
This guide explains how to upgrade your ADF v4.2 project to work with v4.3. | ||
|
||
Do not skip this task, if you want your application to be updated to a most recent version of ADF. | ||
Upgrades of multiple versions of ADF cannot be done in one step only, but should follow the chain of sequential updates. | ||
|
||
**Note:** the steps described below might involve making changes | ||
to your code. If you are working with a versioning system then you should | ||
commit any changes you are currently working on. If you aren't using versioning | ||
then be sure to make a backup copy of your project before going ahead with the | ||
upgrade. | ||
|
||
This guide explains how to upgrade your ADF v3.2 project to work with v3.3. | ||
|
||
Do not skip this task, if you want your application to be updated to a most recent version of ADF. Upgrades of multiple versions of ADF cannot be done in one step only, but should follow the chain of sequential updates. | ||
|
||
**Note:** the steps described below might involve making changes | ||
to your code. If you are working with a versioning system then you should | ||
commit any changes you are currently working on. If you aren't using versioning | ||
then be sure to make a backup copy of your project before going ahead with the | ||
upgrade. | ||
|
||
## Library updates | ||
|
||
### Automatic update using the Yeoman Generator | ||
|
||
If your application has few changes from the original app created by the | ||
[Yeoman generator](https://github.com/Alfresco/generator-ng2-alfresco-app) | ||
then you may be able to update your project with the following steps: | ||
|
||
1. Update the Yeoman generator to the latest version. Note that | ||
you might need to run these commands with `sudo` on Linux or MacOS: | ||
|
||
```sh | ||
npm uninstall -g generator-alfresco-adf-app | ||
npm install -g generator-alfresco-adf-app | ||
``` | ||
|
||
2. Run the new yeoman app generator: | ||
|
||
```sh | ||
yo alfresco-adf-app | ||
``` | ||
|
||
3. Clean your old distribution and dependencies by deleting the `node_modules` folder | ||
and the `package-lock.json` file. | ||
|
||
4. Install the dependencies: | ||
```sh | ||
npm install | ||
``` | ||
|
||
At this point, the generator might have overwritten some of your code where it differs from | ||
the original generated app. Be sure to check for any differences from your project code | ||
(using a versioning system might make this easier) and if there are any differences, | ||
retrofit your changes. When you have done this, you should be able to start the application | ||
as usual: | ||
|
||
```sh | ||
npm run start | ||
``` | ||
|
||
After starting the app, if everything is working fine, that's all and you don't need to do anything else. However, if things don't work as they should then recover the original version of the project and try the manual approach. | ||
### Manual update | ||
1. Update the `package.json` file with the latest library versions: | ||
```json | ||
"dependencies": { | ||
... | ||
"@alfresco/adf-core": "4.3.0", | ||
"@alfresco/adf-content-services": "4.3.0", | ||
"@alfresco/adf-process-services-cloud": "4.3.0", | ||
"@alfresco/adf-insights": "4.3.0", | ||
"@alfresco/js-api": "4.3.0", | ||
... | ||
``` | ||
2. Clean your old distribution and dependencies by deleting `node_modules` and `package-lock.json`. | ||
3. Reinstall your dependencies | ||
```sh | ||
npm install | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,89 @@ | ||
--- | ||
Title: Upgrading from ADF v4.3 to v4.4 | ||
--- | ||
|
||
# Upgrading from ADF v4.3 to v4.4 | ||
|
||
This guide explains how to upgrade your ADF v4.3 project to work with v4.4. | ||
|
||
Do not skip this task, if you want your application to be updated to a most recent version of ADF. | ||
Upgrades of multiple versions of ADF cannot be done in one step only, but should follow the chain of sequential updates. | ||
|
||
**Note:** the steps described below might involve making changes | ||
to your code. If you are working with a versioning system then you should | ||
commit any changes you are currently working on. If you aren't using versioning | ||
then be sure to make a backup copy of your project before going ahead with the | ||
upgrade. | ||
|
||
This guide explains how to upgrade your ADF v4.3 project to work with v4.4. | ||
|
||
Do not skip this task, if you want your application to be updated to a most recent version of ADF. Upgrades of multiple versions of ADF cannot be done in one step only, but should follow the chain of sequential updates. | ||
|
||
**Note:** the steps described below might involve making changes | ||
to your code. If you are working with a versioning system then you should | ||
commit any changes you are currently working on. If you aren't using versioning | ||
then be sure to make a backup copy of your project before going ahead with the | ||
upgrade. | ||
|
||
## Library updates | ||
|
||
### Automatic update using the Yeoman Generator | ||
|
||
If your application has few changes from the original app created by the | ||
[Yeoman generator](https://github.com/Alfresco/generator-ng2-alfresco-app) | ||
then you may be able to update your project with the following steps: | ||
|
||
1. Update the Yeoman generator to the latest version. Note that | ||
you might need to run these commands with `sudo` on Linux or MacOS: | ||
|
||
```sh | ||
npm uninstall -g generator-alfresco-adf-app | ||
npm install -g generator-alfresco-adf-app | ||
``` | ||
|
||
2. Run the new yeoman app generator: | ||
|
||
```sh | ||
yo alfresco-adf-app | ||
``` | ||
|
||
3. Clean your old distribution and dependencies by deleting the `node_modules` folder | ||
and the `package-lock.json` file. | ||
|
||
4. Install the dependencies: | ||
```sh | ||
npm install | ||
``` | ||
|
||
At this point, the generator might have overwritten some of your code where it differs from | ||
the original generated app. Be sure to check for any differences from your project code | ||
(using a versioning system might make this easier) and if there are any differences, | ||
retrofit your changes. When you have done this, you should be able to start the application | ||
as usual: | ||
|
||
```sh | ||
npm run start | ||
``` | ||
|
||
After starting the app, if everything is working fine, that's all and you don't need to do anything else. However, if things don't work as they should then recover the original version of the project and try the manual approach. | ||
### Manual update | ||
1. Update the `package.json` file with the latest library versions: | ||
```json | ||
"dependencies": { | ||
... | ||
"@alfresco/adf-core": "4.4.0", | ||
"@alfresco/adf-content-services": "4.4.0", | ||
"@alfresco/adf-process-services-cloud": "4.4.0", | ||
"@alfresco/adf-insights": "4.4.0", | ||
"@alfresco/js-api": "4.4.0", | ||
... | ||
``` | ||
2. Clean your old distribution and dependencies by deleting `node_modules` and `package-lock.json`. | ||
3. Reinstall your dependencies | ||
```sh | ||
npm install | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
Title: Audit info, alfresco-ng2-components 4.4.0 | ||
--- | ||
|
||
# Audit information for alfresco-ng2-components 4.4.0 | ||
|
||
This page lists the security audit of the dependencies this project depends on. | ||
|
||
## Risks | ||
|
||
- Critical risk: 0 | ||
- High risk: 0 | ||
- Moderate risk: 0 | ||
- Low risk: 0 | ||
|
||
Dependencies analyzed: 729 | ||
|
||
## Libraries | ||
|
||
| Severity | Module | Vulnerable versions | | ||
| --- | --- | --- | | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.