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

chore: let's not store the release notes in the repository #1120

Merged
merged 6 commits into from
Nov 22, 2024

Conversation

hilmarf
Copy link
Member

@hilmarf hilmarf commented Nov 21, 2024

What this PR does / why we need it

It's one step to "Simplify management of Release Notes" - #1097

@hilmarf hilmarf added this to the 2024-Q4 milestone Nov 21, 2024
@github-actions github-actions bot added component/github-actions Changes on GitHub Actions or within `.github/` directory chore size/l Large labels Nov 21, 2024
@hilmarf hilmarf marked this pull request as ready for review November 21, 2024 11:17
@hilmarf hilmarf requested a review from a team as a code owner November 21, 2024 11:17
Copy link
Contributor

github-actions bot commented Nov 21, 2024

Mend Scan Summary: ❌

Repository: open-component-model/ocm

VIOLATION DESCRIPTION NUMBER OF VIOLATIONS
HIGH/CRITICAL SECURITY VULNERABILITIES 4
MAJOR UPDATES AVAILABLE 0
LICENSE REQUIRES REVIEW 2
HIGH RISK LICENSES 10
RESTRICTIED LICENSE FOR ON-PREMISE DELIVERY 0

Detailed Logs: mend-scan-> Generate Report
Mend UI

hack/winget/README.md Show resolved Hide resolved
RELEASE_PROCESS.md Show resolved Hide resolved
Copy link
Contributor

@jakobmoellerdev jakobmoellerdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay for me but we will need to manually maintain release notes through github releases then

@hilmarf hilmarf enabled auto-merge (squash) November 22, 2024 09:25
Copy link
Contributor

@jakobmoellerdev jakobmoellerdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM we have to deal with candidate notes manually for now

@hilmarf hilmarf merged commit a061dfd into main Nov 22, 2024
23 checks passed
@hilmarf hilmarf deleted the chore/release_notes branch November 22, 2024 09:35
jakobmoellerdev added a commit that referenced this pull request Nov 22, 2024
<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it

Makes sure that release notes are correctly drawn in and that we always
have the version set correctly in our CTFs.

#### Which issue(s) this PR fixes
<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

This fixes up the release action in 2 important ways:

1. As part of the removal of the release notes we now no longer have a
file to use for release notes to give to goreleaser. This means we have
to temporarily create one
2. While discovering this I noticed that the Component Versions that are
built, are actually using the `VERSION` variable while
`EFFECTIVE_VERSION` is a combination of VERSION+COMMIT by default. I
didnt want to change this behavior originally, so now I started to use
VERSION for the Makefiles (which also means I had to export them as
settable). This now leads to correct CTF versions `v0.19.0-rc.1` instead
of `v0.19.0-dev` for example.

As such its a follow up from
#1120 and
#1077
@hilmarf hilmarf added the kind/chore chore, maintenance, etc. label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/github-actions Changes on GitHub Actions or within `.github/` directory kind/chore chore, maintenance, etc. size/l Large
Projects
Status: 🔒Closed
Development

Successfully merging this pull request may close these issues.

3 participants