Skip to content

Conversation

@donsizemore
Copy link
Contributor

What this PR does / why we need it:

bumps everit-json-schema which in turn updates org.json

Which issue(s) this PR closes:

partially addresses https://github.com/IQSS/dataverse-security/issues/89

Special notes for your reviewer:

none

Suggestions on how to test this:

standard test suite, any particular/custom JSON input

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

no

Is there a release notes update needed for this change?:

no

Additional documentation:

none

@donsizemore donsizemore requested a review from qqmyers November 13, 2025 21:14
@coveralls
Copy link

Coverage Status

coverage: 23.803%. remained the same
when pulling 6259514 on 89_bump_org_json
into b78060a on develop.

@github-actions
Copy link

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:89-bump-org-json
ghcr.io/gdcc/configbaker:89-bump-org-json

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

Copy link
Member

@qqmyers qqmyers left a comment

Choose a reason for hiding this comment

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

Looks fine

@qqmyers qqmyers moved this to Ready for Triage in IQSS Dataverse Project Nov 13, 2025
@qqmyers qqmyers added the Size: 0.5 A percentage of a sprint. 0.35 hours label Nov 13, 2025
@scolapasta scolapasta moved this from Ready for Triage to Ready for QA ⏩ in IQSS Dataverse Project Nov 20, 2025
@cmbz cmbz added the FY26 Sprint 11 FY26 Sprint 11 (2025-11-20 - 2025-12-03) label Nov 22, 2025
@cmbz cmbz added the FY26 Sprint 12 FY26 Sprint 12 (2025-12-03 - 2025-12-17) label Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

FY26 Sprint 11 FY26 Sprint 11 (2025-11-20 - 2025-12-03) FY26 Sprint 12 FY26 Sprint 12 (2025-12-03 - 2025-12-17) Size: 0.5 A percentage of a sprint. 0.35 hours

Projects

Status: Reviewed but Frozen ❄️

Development

Successfully merging this pull request may close these issues.

5 participants