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

Is it possible to reuse changelog information from Renovate? #234

Open
oed-guzym opened this issue Jun 1, 2022 · 0 comments
Open

Is it possible to reuse changelog information from Renovate? #234

oed-guzym opened this issue Jun 1, 2022 · 0 comments

Comments

@oed-guzym
Copy link

Hello everyone,

we are currently using Renovate to regularly check the dependencies of our Umbrella Charts (Helm) for updates. Afterwards, we receive a merge request and manually create a new tag for our charts, which we then use to update our applications in a Kubernetes environment using ArgoCD.

Now we want to automate the manual process of our release management with semantic-release, so that we don't have to constantly check for new merge requests and process them.

So far, we can already create and use a new tag in GitLab via semantic-release based on the commits created by Renovate. Now we come to the point where we think about the changelog and ask whether it is possible to reuse the changelog provided by Renovate in the merge request.

For example, a merge request from Renovate may have the following content:
Renovate_MR

The commit of Renovate itself is relatively uninformative and looks like this:
Renovate_Commit

The changelog created by semantic-release would only contain the one entry with the reference to the update, based on the commit. But Renovate itself provides much more information.

Is there a possibility to access this information via a plugin or possibly in other ways? Does anyone have any experience or an alternative how we can get more information about the update?

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

No branches or pull requests

1 participant