fix: empty the contents of the dependencyVersions.properties file when creating it #1213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found that my dependencyVersions.properties and sdkVersions.properties files had thousands of lines in them, which is redundant.
The build process creates these files by reading the package json versions of AWS code and of Smithy packages.
These file numbers are used in our dependency enums when initializing an enum value with no particular version number:
During releases to maven, the then-current versions within the workspace are stamped into the maven artifact. Since the action appends the version to the end of the file, presumably the latest versions will be written in the HashMap, regardless of what may exist already in the file.
There was a report that 0.19.0 of the smithy-aws-typescript-codegen package had duplicate entries in the
sdkVersions.properties
file.