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

merge master into prod in preparation of release v2.0.0 #607

Merged
merged 131 commits into from
Oct 28, 2024
Merged

merge master into prod in preparation of release v2.0.0 #607

merged 131 commits into from
Oct 28, 2024

Conversation

ljones140
Copy link
Contributor

Test what is happening

yashkohli88 and others added 30 commits January 30, 2024 13:42
document._metadata.links.self.href is used in construct file path or blob name when storing the harvested data.  It should reflect the _schemaVersion of PodExtract.  Added test to verify this.
1. In AbstractProcessor, _schemaVersion is the combination of schemaVersion or toolVersion along the class hierarchy.
2. Most component related processors, e.g. mavenExtract or npmExtract, which are subClasses of abstractClealyDefinedProcessors, overrride toolVersion(),  see comments at AbstractProcessor.toolVersion().
This convention was introduced in commit "isolate toolVersion from schemaVersion".

The exception is PodExtract.  This commit aligns PodExtract with the rest of the component related processors.
This is for fix to exclude .git directory content in recent PR (#525).
Bump up the version to allow reharvest of pod components.
The recent fix to exclude content in the .git directory (#525) from pod packages will cause the file count to be different from the previous version. Update the toolVersion for PodExtract to 2.0.0 to reflect this.
@ljones140 ljones140 marked this pull request as draft October 18, 2024 17:10
@elrayle elrayle changed the title test the release merge master into prod in preparation of release v2.0.0 Oct 21, 2024
@elrayle elrayle merged commit 284d8f8 into prod Oct 28, 2024
16 of 18 checks passed
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.

None yet

7 participants