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
Entries should focus on the changes that users need to make when upgrading
177
-
to `{{% param "majorVersion" %}}`, rather than how to write configurations
178
-
after upgrading.
179
-
180
-
See [Terraform provider for Google Cloud 5.0.0 Upgrade Guide](https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/version_5_upgrade)
181
-
and other upgrade guides for examples.
182
-
183
-
The upgrade guide and the actual breaking change will be merged only after both are completed.
184
-
185
-
### Make the breaking change on `FEATURE-BRANCH-major-release-{{% param "majorVersion" %}}`
172
+
### Make the change on `FEATURE-BRANCH-major-release-{{% param "majorVersion" %}}`
186
173
187
174
When working on your breaking change, make sure that your base branch
188
175
is `FEATURE-BRANCH-major-release-{{% param "majorVersion" %}}`. This
@@ -207,14 +194,17 @@ with the following changes:
207
194
are present on the major release branch. Changes to the `main` branch will be
208
195
merged into the major release branch every Monday.
209
196
1. Make the breaking change.
197
+
1. Add the upgrade guide entries to
198
+
[{{< param upgradeGuide >}}](https://github.com/GoogleCloudPlatform/magic-modules/blob/FEATURE-BRANCH-major-release-6.0.0/mmv1/third_party/terraform/website/docs/guides/{{< param upgradeGuide >}}). Entries should focus on the changes that users need to make when upgrading
199
+
to `{{% param "majorVersion" %}}`, rather than how to write configurations
200
+
after upgrading. See [Terraform provider for Google Cloud 5.0.0 Upgrade Guide](https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/version_5_upgrade)
201
+
and other upgrade guides for examples.
210
202
1. Remove any deprecation notices and warnings (including in documentation) not already removed by the breaking change.
211
203
1. When you create your pull request,
212
204
[change the base branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)
213
205
to `FEATURE-BRANCH-major-release-{{% param "majorVersion" %}}`
214
206
1. To resolve merge conflicts with `git rebase` or `git merge`, use `FEATURE-BRANCH-major-release-{{% param "majorVersion" %}}` instead of `main`.
215
207
216
-
The upgrade guide and the actual breaking change will be merged only after both are completed.
0 commit comments