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

Cherry-pick PR 579 and PR 584 #588

Merged
merged 2 commits into from
Dec 16, 2024
Merged

Cherry-pick PR 579 and PR 584 #588

merged 2 commits into from
Dec 16, 2024

Conversation

tiagolobocastro
Copy link
Contributor

chore: fix helm-testing versioning in publish-chart-yaml

Replace hard coded patch and minor values of 0,
with values derived from the chart version

That way we get versions derived from chart/Chart.yaml,
like 2.7.2-... instead of hard coded values like 2.7.0-... or 2.0.0-....

Signed-off-by: Blaise Dias <[email protected]>

ci: various release chart update fixes

Don't update the chart on a pre-release
Set missing base branch for pull-request
Add stricter release validation
Add more tests

Signed-off-by: Tiago Castro <[email protected]>

tiagolobocastro and others added 2 commits December 13, 2024 22:54
Don't update the chart on a pre-release
Set missing base branch for pull-request
Add stricter release validation
Add more tests

Signed-off-by: Tiago Castro <[email protected]>
Replace hard coded patch and minor values of 0,
with values derived from the chart version

That way we get versions derived from chart/Chart.yaml,
like 2.7.2-... instead of hard coded values like 2.7.0-... or 2.0.0-....

Signed-off-by: Blaise Dias <[email protected]>
@tiagolobocastro
Copy link
Contributor Author

bors merge

bors-openebs-mayastor bot pushed a commit that referenced this pull request Dec 16, 2024
588: Cherry-pick PR 579 and PR 584 r=tiagolobocastro a=tiagolobocastro

    chore: fix helm-testing versioning in publish-chart-yaml
    
    Replace hard coded patch and minor values of 0,
    with values derived from the chart version
    
    That way we get versions derived from chart/Chart.yaml,
    like 2.7.2-... instead of hard coded values like 2.7.0-... or 2.0.0-....
    
    Signed-off-by: Blaise Dias <[email protected]>



Co-authored-by: Tiago Castro <[email protected]>
Co-authored-by: Blaise Dias <[email protected]>
@bors-openebs-mayastor
Copy link
Contributor

This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried.

Additional information:

Response status code: 422
{"message":"Required status check \"template-chart\" is failing.","documentation_url":"https://docs.github.com/articles/about-protected-branches","status":"422"}

@tiagolobocastro
Copy link
Contributor Author

Network error it seems...
bors merge

bors-openebs-mayastor bot pushed a commit that referenced this pull request Dec 16, 2024
588: Cherry-pick PR 579 and PR 584 r=tiagolobocastro a=tiagolobocastro

    chore: fix helm-testing versioning in publish-chart-yaml
    
    Replace hard coded patch and minor values of 0,
    with values derived from the chart version
    
    That way we get versions derived from chart/Chart.yaml,
    like 2.7.2-... instead of hard coded values like 2.7.0-... or 2.0.0-....
    
    Signed-off-by: Blaise Dias <[email protected]>



Co-authored-by: Tiago Castro <[email protected]>
Co-authored-by: Blaise Dias <[email protected]>
@bors-openebs-mayastor
Copy link
Contributor

This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried.

Additional information:

Response status code: 422
{"message":"Required status check \"template-chart\" is failing.","documentation_url":"https://docs.github.com/articles/about-protected-branches","status":"422"}

@tiagolobocastro
Copy link
Contributor Author

bors merge

@bors-openebs-mayastor
Copy link
Contributor

Build succeeded:

@bors-openebs-mayastor bors-openebs-mayastor bot merged commit 8f85073 into develop Dec 16, 2024
7 checks passed
@bors-openebs-mayastor bors-openebs-mayastor bot deleted the dev-rel-fixes branch December 16, 2024 11:34
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.

5 participants