-
Notifications
You must be signed in to change notification settings - Fork 41
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 for v1.3.0 release #1118
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
removed extra semicolon added architecture to conda revisions removed base version fix version fetching fixed lint errors update added tests Fix license not detected for some maven packages When processing scancode result, license information is first derived from package level data. When this is not available, ScanCodeSummarizer goes through the root files to look for license. Filtering for root files is based on case sensitive file path matching. In maven packaging, META/INF directory is the standard (see https://issues.apache.org/jira/browse/MJAR-73?attachmentOrder=desc, and https://issues.apache.org/jira/browse/MEAR-30). Change the location for maven to reflect the casing. utils.getLicenseLocations is also used in utils.isLicenseFile. isLicenseFile uses case insensitive matching. Preserve this case insensitive file path matching by converting the result from getLicenseLocations to lowercase there. Test case: https://clearlydefined.io/definitions/maven/mavencentral/org.flywaydb/flyway-core/9.20.0 https://dev.clearlydefined.io/definitions/maven/mavencentral/org.flywaydb/flyway-core/7.7.2 Task: #846 Fix license detection for some sourcearchive packages Task: clearlydefined/crawler#533 fixed test update
Co-authored-by: lisahoong <lhoong94@gmail.com>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.1.0 to 5.2.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v5.1.0...v5.2.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [azure/login](https://github.com/azure/login) from 1.6.1 to 2.0.0. - [Release notes](https://github.com/azure/login/releases) - [Commits](Azure/login@v1.6.1...v2.0.0) --- updated-dependencies: - dependency-name: azure/login dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…ecrets Revert "remove docker secrets from deploy action"
…elr/remove-secrets Revert "Revert "remove docker secrets from deploy action""
…s/azure/login-2.0.0 Bump azure/login from 1.6.1 to 2.0.0
…s/docker/build-push-action-5.2.0 Bump docker/build-push-action from 5.1.0 to 5.2.0
Bumps the azure-actions group with 2 updates: [azure/login](https://github.com/azure/login) and [azure/webapps-deploy](https://github.com/azure/webapps-deploy). Updates `azure/login` from 2.0.0 to 2.1.0 - [Release notes](https://github.com/azure/login/releases) - [Commits](Azure/login@v2.0.0...v2.1.0) Updates `azure/webapps-deploy` from 3.0.0 to 3.0.1 - [Release notes](https://github.com/azure/webapps-deploy/releases) - [Commits](Azure/webapps-deploy@v3.0.0...v3.0.1) --- updated-dependencies: - dependency-name: azure/login dependency-type: direct:production update-type: version-update:semver-minor dependency-group: azure-actions - dependency-name: azure/webapps-deploy dependency-type: direct:production update-type: version-update:semver-patch dependency-group: azure-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the docker-actions group with 2 updates: [docker/login-action](https://github.com/docker/login-action) and [docker/build-push-action](https://github.com/docker/build-push-action). Updates `docker/login-action` from 3.0.0 to 3.1.0 - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@v3.0.0...v3.1.0) Updates `docker/build-push-action` from 5.2.0 to 5.3.0 - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v5.2.0...v5.3.0) --- updated-dependencies: - dependency-name: docker/login-action dependency-type: direct:production update-type: version-update:semver-minor dependency-group: docker-actions - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor dependency-group: docker-actions ... Signed-off-by: dependabot[bot] <support@github.com>
…s/azure-actions-e950c8c083 Bump the azure-actions group with 2 updates
…s/peter-evans/create-pull-request-6.0.4 Bump peter-evans/create-pull-request from 6.0.1 to 6.0.4
…s/docker-actions-2ff959799f Bump the docker-actions group with 2 updates
Separate aggregator related tests to aggregatorTest.js
Whether packages contain source files depends on the package type, not the package provider. Change the logic to build source location to reflect this.
* use consistent naming for build-and-deploy workflows * make workflow display name easier to scan
use shared dev deploy workflow in operations
Add source location in definitions for sourcearchive packages
Add a simple test for conda revisions route
[conda] fixed service component bug
Fix originConda route
Update test workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.