Hello everyone,
Please apologize the reaction being sent as a reply-all to the list.
Together with that positive feedback, I want to thank you Tomasz for the Dependabot TRG and ask if there is any plan on how to move forward with some specific dependency update in case it breaks the build.
In the past, on a small team, I had a good experience closing those Dependabot PRs and opening a ticket to investigate and fix that specific update.
Also, it can be helpful to have documented for each project the list of “non-updatable dependencies”, as they might incur breaking changes, re-work, or any other consequence that blocks a library to be updated
to a specific version.
Any thoughts about that?
Thank you.
Felipe Zampa Fonseca
Application Architect Core Services
Cofinity-X GmbH │c/o Im Mediapark 5 │50670 Köln
E : felipe.zampa@xxxxxxxxxxxxxx
M : +49 176 15344601
Booking | LinkedIn

Mandatory Disclosure Statement: www.cofinity-x.com/impressum
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified, that any review, copying, or distribution
of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
From:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Tomasz.Barwicki--- via tractusx-dev <tractusx-dev@xxxxxxxxxxx>
Date: Tuesday, January 16, 2024 at 12:27
To: tractusx-dev@xxxxxxxxxxx <tractusx-dev@xxxxxxxxxxx>
Cc: Tomasz.Barwicki@xxxxxxxxxxxxx <Tomasz.Barwicki@xxxxxxxxxxxxx>
Subject: [tractusx-dev] New Dependabot Tractus-X Release Guideline
Dear Tractus-X Community,
I hope this email finds you well. I’m
excited to share an
update regarding new
GitHub Dependabot Tractus-X Release Guideline.
The aim of the TRG is to help us automatically track and manage dependencies, ensuring that our projects
remain secure and up to date.
The document is currently available in draft form and is ready for your review.
You can access the document
here.
Encourage you to review the document at your earliest convenience. Feel free to share any comments, suggestions, or questions you may have directly on the document or by replying to
this email.
Thank you for your continued support and collaboration.
Best regards,
Tomasz Barwicki