-
Notifications
You must be signed in to change notification settings - Fork 580
Return atomic flag in the upgrade docs #1960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
TerryHowe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These documents are generated, so while your pull request is correct it makes me think there are likely other errors here and it should be regenerated.
|
Hmm... I thought that it could be generated but I expected a different folder for that. Like |
Signed-off-by: Sergey Tarasov <[email protected]> Signed-off-by: Tarasov Sergey <[email protected]>
Signed-off-by: Sergey Tarasov <[email protected]> Signed-off-by: Tarasov Sergey <[email protected]>
Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.3.1 to 1.3.2. - [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md) - [Commits](digitalbazaar/forge@v1.3.1...v1.3.2) --- updated-dependencies: - dependency-name: node-forge dependency-version: 1.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Tarasov Sergey <[email protected]>
Signed-off-by: Tarasov Sergey <[email protected]>
Signed-off-by: Tarasov Sergey <[email protected]>
|
I regenerated CLI docs and updated the current versions. |

I've noticed that the third version of upgrade command contains a new flag. But the previous one was deleted.