Skip to content
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

Backport of Fix for incorrect rendering of > as ≥ in version constraints into v1.2 #36046

Conversation

github-actions[bot]
Copy link
Contributor

Backport

This PR is auto-generated from #36044 to be assessed for backporting due to the inclusion of the label 1.2-backport.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@trujillo-adam
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/terraform/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Our docs platform automatically adds links to words at the beginning of a list item when the words are formatted with code backticks. And because links are automatically style with an underline, the < character becomes underlined, which changes the meaning. This PR changes the list of operators you can use to constrain versions into a table, which omits the autogenerated links.

I also made some content updates for compliance with our writing style guidelines.

Fixes #32423

Target Release

Backports for all versions going back to 1.1.


Overview of commits

Copy link

hashicorp-cla-app bot commented Nov 19, 2024

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • trujillo-adam
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

…nts-operators-reference

Fix for incorrect rendering of > as ≥ in version constraints
Fixed merge conflicts
@trujillo-adam trujillo-adam merged commit 5d5bbcd into v1.2 Nov 19, 2024
5 of 6 checks passed
@trujillo-adam trujillo-adam deleted the backport/docs/update-version-constraints-operators-reference/firmly-classic-wombat branch November 19, 2024 17:35
Copy link
Contributor Author

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant