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

update go-cty to latest patch release #36376

Merged
merged 2 commits into from
Jan 22, 2025
Merged

update go-cty to latest patch release #36376

merged 2 commits into from
Jan 22, 2025

Conversation

liamcervante
Copy link
Member

@liamcervante liamcervante commented Jan 22, 2025

Update to the latest patch release of go-cty. As this is a patch release that contains only bug fixes we should be safe to backport to 1.10 to fix the underlying issue there as well.

Fixes #36369
Fixes #36351

Target Release

1.10.x

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

@liamcervante liamcervante added the 1.10-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged label Jan 22, 2025
@liamcervante liamcervante requested review from a team as code owners January 22, 2025 07:30
dsa0x
dsa0x previously approved these changes Jan 22, 2025
@dbanck
Copy link
Member

dbanck commented Jan 22, 2025

I believe this also fixes #36351 and might warrant a second changelog entry for that?

@liamcervante
Copy link
Member Author

Nice! Yeah, it does. Added a new changelog entry for that, and updated the description.

@liamcervante liamcervante requested review from dsa0x and a team January 22, 2025 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.10-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged
Projects
None yet
3 participants