json-schema-org / landscape

The JSON Schema Landscape
https://landscape.json-schema.org/
10 stars 11 forks source link

update to latest landscape structure for tooling workflow #73

Closed DarhkVoyd closed 4 months ago

DarhkVoyd commented 4 months ago

What kind of change does this PR introduce? The current landscape.yml is following an outdated structure with nullish keys, which is an interruption for landscape's tooling automation workflow. This PR aims to update landscape.yml to follow the latest structure which is cleaner and update the landscape2 version that supports it.

Issue Number:

Screenshots/videos:

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

DarhkVoyd commented 4 months ago

The build workflow fails as this the older landscape tool version expects the root field to be "landscape", updating the "landscape2" to the latest version fixes this which is included in the PR.

benjagm commented 4 months ago

Hi DV. The CI/CD workflow failed here: https://github.com/json-schema-org/landscape/actions/runs/10092190239

Can you please check it?

DarhkVoyd commented 4 months ago

The build workflow fails as this the older landscape tool version expects the root field to be "landscape", updating the "landscape2" to the latest version fixes this which is included in the PR.

Yeah, as I mentioned earlier the CI/CD workflow is failing because of the above reason, this PR also updates the landscape version from 0.9 to 0.10, that will fix the build error.

benjagm commented 4 months ago

The build workflow fails as this the older landscape tool version expects the root field to be "landscape", updating the "landscape2" to the latest version fixes this which is included in the PR.

Yeah, as I mentioned earlier the CI/CD workflow is failing because of the above reason, this PR also updates the landscape version from 0.9 to 0.10, that will fix the build error.

Thanks DV. I was just double-checking. PR Merged.

DarhkVoyd commented 4 months ago

Great, the landscape has been build and deployed without any errors. While the validation workflow has failed due to toomanyrequests apparently. Using default tag: latest Error response from daemon: toomanyrequests: Data limit exceeded Warning: Docker pull failed with exit code 1, back off 7.218 seconds before retry.