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

Go119 bump (#1) #2373

Merged
merged 1 commit into from
Feb 16, 2023
Merged

Go119 bump (#1) #2373

merged 1 commit into from
Feb 16, 2023

Conversation

gururajsh
Copy link
Member

@gururajsh gururajsh commented Feb 15, 2023

  • Upgrades go from 1.18 to 1.19

Thank you for contributing to the CF CLI! Please read the following:

  • Please make sure you have implemented changes in line with the contributing guidelines
  • We're not allowed to accept any PRs without a signed CLA, no matter how small.
    If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
  • All new code requires tests to protect against regressions.
  • Contributions must be made against the appropriate branch. See the contributing guidelines
  • Contributions must conform to our style guide. Please reach out to us if you have questions.

Does this PR modify CLI v6, CLI v7, or CLI v8?

No

Description of the Change

Golang version upgrade from 1.18 to 1.19

Why Is This PR Valuable?

What benefits will be realized by the code change? What users would want this change? What user need is this change addressing?
Golang 1.19 is more secure, addresses CVEs which is useful for users.

Why Should This Be In Core?

Explain why this functionality should be in the cf CLI, as opposed to a plugin.
Because cf cli is written in golang.

Applicable Issues

List any applicable GitHub Issues here

How Urgent Is The Change?

Is the change urgent? If so, explain why it is time-sensitive.

Other Relevant Parties

Who else is affected by the change?

* Upgrades go from 1.18 to 1.19

---------

Co-authored-by: Juan Diego Gonzalez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants