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 Porter to v1.0.9 #230

Merged
merged 2 commits into from
Feb 24, 2023
Merged

Update Porter to v1.0.9 #230

merged 2 commits into from
Feb 24, 2023

Conversation

carolynvs
Copy link
Member

@carolynvs carolynvs commented Feb 22, 2023

  • Update porter to v1.0.9
  • Update magefiles to v0.5.0 so that releases generate an arm64 binary

NOTE: I tried to update to the latest operator version and realized that more work is needed to do that so I'm limiting this PR to just the security updates.

@carolynvs carolynvs force-pushed the bump-porter branch 3 times, most recently from 60186bc to fd83b5e Compare February 24, 2023 16:43
@sgettys
Copy link
Collaborator

sgettys commented Feb 24, 2023

Just something I thought of for plugins will porter automatically install the appropriate architecture when you run plugin install?

@carolynvs
Copy link
Member Author

I just backed out the update to the latest version of the operator since there's more work to be done there first. All of the tests are failing because of an error in the operator. So this PR is going to just have the security patches, but otherwise remain on the older version of the operator for tests.

To your question, the porter plugins install command takes into account the client architecture when downloading. If an arm binary is available, it is used, otherwise porter falls back to amd64 and hopes rosetta is installed (for macs).

* Update porter to v1.0.9
* Update golang.org/x/crypto to v0.6.0

Signed-off-by: Carolyn Van Slyck <[email protected]>
The latest magefiles generates an arm64 binary during a release

Signed-off-by: Carolyn Van Slyck <[email protected]>
@carolynvs carolynvs merged commit 0bc05c9 into getporter:main Feb 24, 2023
@carolynvs carolynvs deleted the bump-porter branch February 24, 2023 17:41
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.

2 participants