Skip to content

Bump image for April CU #368

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

Open
wants to merge 1 commit into
base: testing
Choose a base branch
from

Conversation

Copy link
Collaborator

@vnaren23 vnaren23 left a comment

Choose a reason for hiding this comment

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

Shouldn't we be adding new files rather than editing existing ones? @irinel-birsan-uipath can you comment?

@irinel-birsan-uipath
Copy link
Member

irinel-birsan-uipath commented Mar 13, 2025

Shouldn't we be adding new files rather than editing existing ones? @irinel-birsan-uipath can you comment?

From a technical perspective, this is ok, meaning that, for new installations, only the new version will be available.
In DU, we used to create a new version for each new CVE fixed, which resulted in hundreds of new versions. We gave up in doing so, and for CVEs fixes, we only keep the last patch, and we remove the old versions.

Can it be an issue from the support perspective? e.g. we need to keep each version for three years and so? Only the new installations are affected. The old customer will still have all the versions so I would say it is ok.

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.

4 participants