You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs-sources/patcher/running-patcher/update.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,36 +25,33 @@ If Patcher can update one or more usages of a module to a newer version, then Pa
25
25
26
26
* "Hit «b» to update all usages to the next version, even if it's a breaking change."
27
27
28
-
28
+
29
29
30
30
Pressing `ENTER` will update all the usages of that module to either the highest version before the next closest breaking change or the latest version of the dependecy, whichever is encountered first.
31
31
32
32
Pressing `b` will update all the usages of that module to either the next closest breaking change or the latest version of the dependency, whichever is encountered first.
33
33
34
34
After updating the "Up to date" column is changed to show "Updated". This indicates that at least one of the dependencies on that module have been updated.
35
35
36
-
36
+
37
37
38
38
When you quit Patcher, it writes the details of all the updates to stdout in YAML format, for example:
Starting in `0.3.3`, Patcher provides limited support for updating third party modules, this includes your own modules. The updates to third party module are limited to bumping the semver patch version.
88
+
Beginning with version `0.3.3`, Patcher provides limited support for updating third party modules, including your own modules. The updates to third party module are limited to bumping the semver patch version.
92
89
93
90
Third party modules are supported in both interactive mode and non-interactive mode.
Copy file name to clipboardExpand all lines: _docs-sources/patcher/update-strategies.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,11 +45,11 @@ This is an example of the YAML that Patcher writes to `stdout` describing these
45
45
46
46
The **next breaking** strategy will update a dependency to either the next closest breaking change or the latest version of the dependency, whichever is encountered first.
47
47
48
-
So if Patcher encounters a breaking change that it cannot patch then it will update the dependencies to the version with the breaking change and stop. Otherwise, if no breaking chnages are encountered it will update the dependencies the latest version of that module.
48
+
So if Patcher encounters a breaking change that it cannot patch then it will update the dependencies to the version with the breaking change and stop. Otherwise, if no breaking changes are encountered it will update the dependencies the latest version of that module.
49
49
50
50
This may result in an update that requires manual intervention. If so, Patcher will provide additional information to help you understand what needs to be done.
51
51
52
-
Patcher does this by writing a `README-TO-COMPLETE-UPDATE.md` into the folder containing the dependendency. If more than one dependency in a folder has been update to a breaking version, then the `README-TO-COMPLETE-UPDATE.md` file will contain a release note extracts for each breaking change in that folder.
52
+
Patcher does this by writing a `README-TO-COMPLETE-UPDATE.md` into the folder containing the dependency. If more than one dependency in a folder has been updated to a breaking version, then the `README-TO-COMPLETE-UPDATE.md` file will contain a release note extract for each breaking change in that folder.
53
53
54
54
For example, for the dependencies on `terraform-aws-security/custom-iam-entity` in `infrastructure-live/dev`:
55
55
- `_global/ops-admin-role/terragrunt.hcl`will be updated from `0.65.6` to `0.68.2`, the latest version
Copy file name to clipboardExpand all lines: docs/patcher/running-patcher/update.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,36 +25,33 @@ If Patcher can update one or more usages of a module to a newer version, then Pa
25
25
26
26
* "Hit «b» to update all usages to the next version, even if it's a breaking change."
27
27
28
-
28
+
29
29
30
30
Pressing `ENTER` will update all the usages of that module to either the highest version before the next closest breaking change or the latest version of the dependecy, whichever is encountered first.
31
31
32
32
Pressing `b` will update all the usages of that module to either the next closest breaking change or the latest version of the dependency, whichever is encountered first.
33
33
34
34
After updating the "Up to date" column is changed to show "Updated". This indicates that at least one of the dependencies on that module have been updated.
35
35
36
-
36
+
37
37
38
38
When you quit Patcher, it writes the details of all the updates to stdout in YAML format, for example:
Starting in `0.3.3`, Patcher provides limited support for updating third party modules, this includes your own modules. The updates to third party module are limited to bumping the semver patch version.
88
+
Beginning with version `0.3.3`, Patcher provides limited support for updating third party modules, including your own modules. The updates to third party module are limited to bumping the semver patch version.
92
89
93
90
Third party modules are supported in both interactive mode and non-interactive mode.
94
91
@@ -109,6 +106,6 @@ Patcher cannot update from `4.0.x` to `5.0.0` and will instead show a `?` in the
Copy file name to clipboardExpand all lines: docs/patcher/update-strategies.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,11 +45,11 @@ This is an example of the YAML that Patcher writes to `stdout` describing these
45
45
46
46
The **next breaking** strategy will update a dependency to either the next closest breaking change or the latest version of the dependency, whichever is encountered first.
47
47
48
-
So if Patcher encounters a breaking change that it cannot patch then it will update the dependencies to the version with the breaking change and stop. Otherwise, if no breaking chnages are encountered it will update the dependencies the latest version of that module.
48
+
So if Patcher encounters a breaking change that it cannot patch then it will update the dependencies to the version with the breaking change and stop. Otherwise, if no breaking changes are encountered it will update the dependencies the latest version of that module.
49
49
50
50
This may result in an update that requires manual intervention. If so, Patcher will provide additional information to help you understand what needs to be done.
51
51
52
-
Patcher does this by writing a `README-TO-COMPLETE-UPDATE.md` into the folder containing the dependendency. If more than one dependency in a folder has been update to a breaking version, then the `README-TO-COMPLETE-UPDATE.md` file will contain a release note extracts for each breaking change in that folder.
52
+
Patcher does this by writing a `README-TO-COMPLETE-UPDATE.md` into the folder containing the dependency. If more than one dependency in a folder has been updated to a breaking version, then the `README-TO-COMPLETE-UPDATE.md` file will contain a release note extract for each breaking change in that folder.
53
53
54
54
For example, for the dependencies on `terraform-aws-security/custom-iam-entity` in `infrastructure-live/dev`:
55
55
- `_global/ops-admin-role/terragrunt.hcl`will be updated from `0.65.6` to `0.68.2`, the latest version
@@ -99,6 +99,6 @@ Here are the release notes for version v0.62.0:
0 commit comments