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

component: consistently handle not found errors #430

Merged
merged 2 commits into from
Aug 16, 2023

Conversation

crhntr
Copy link
Contributor

@crhntr crhntr commented Aug 8, 2023

When a github-release source is not found, kiln aborts early without trying additional release sources.

This change ensures the github release source reports "ErrNotFound" so that subsequent release sources can be tried.

Bumped go.mod -go=1.20 to pull in "errors.Join". kiln is already built with Go 1.20 so this seems reasonable.

When a github-release source is not found, kiln aborts early without
trying additional release sources.

This change ensures the github release source reports "ErrNotFound" so
that subsequent release sources can be tried.

Bumped go.mod -go=1.20 to pull in "errors.Join".  kiln is already built
with Go 1.20 so this seems reasonable.
@cf-gitbot
Copy link
Member

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@crhntr
Copy link
Contributor Author

crhntr commented Aug 16, 2023

This change was made by @abg. I am merging it after review.

@crhntr crhntr merged commit e1e0021 into main Aug 16, 2023
3 checks passed
@crhntr crhntr deleted the handle-release-not-found branch August 16, 2023 19:43
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.

3 participants