Repository navigation
chore(atlassian): refresh adf schema provenance to 57.6.21 - #2205
Merged
Merged
Conversation
The upstream full JSON is unchanged; refresh the vendored, generated, and runtime provenance together for the newly pinned tarball. Closes #2199
CoverageTotal: 97.93% ⚪ 0 pp vs Comparing No per-file coverage changes vs 🔇 269 ignored region(s), 0 tolerated region(s)
Patch coverageNo new executable lines added by this diff. |
This file contains hidden or 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
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.
Description
Refresh the pinned
@atlaskit/adf-schemaprovenance from 57.6.19 to 57.6.21 to resolve the automated drift report. The downloaded tarball matches the issue's SHA-256, and its completefull.jsonis byte-for-byte identical to the vendored schema, including attribute and mark constraints. Validation behavior is unchanged.Type of Change
Related Issue
Closes #2199
Implementation plan
Changes Made
assets/adf-schema/provenance.json.src/atlassian/adf_schema/generated.rs; only its version and tarball hash change.SCHEMA_VERSIONto57.6.21-2026-10-06, the runtime tarball hash, and the verification URL insrc/atlassian/adf_schema.rs.full.jsonandCONTENT_ENTRIES. No changelog entry or new tests are needed for this provenance-only refresh.Testing
Checks passed before rebase and were rerun after rebasing onto
origin/main:All cargo invocations used the explicit worktree manifest and working directory; generator inputs/output used absolute worktree paths.
Tarball SHA-256:
9f17f6d3cb3baf053f3ca069d023c0b76e9efda31e5416c903ddf3341449d2be.Both JSON files have SHA-256
5128562b75278c8a83e7e3619a570205bc80d59696985ec31a7a7883cff66fbe, anddiff -ureports no differences.The initial sandboxed schema run passed 99 tests but failed seven mock-server tests because local port binding was denied. Rerunning with local sockets permitted passed all 106; subsequent validation used that environment.
Coverage was not measured locally: no executable logic was added. Other toolchains/platforms, release builds, audit, and dependency-policy checks are left to CI.
Review Focus Areas
Confirm the vendored, generated, and runtime provenance agree. The committed diff and surrounding schema code were reviewed against
origin/main...HEAD: no actionable findings, no fixes or skipped findings. Commit-twiddle validation found the message conformant.Checklist
mainand reran validationPerformance Impact
No performance impact.
Security Considerations
The exact pinned tarball hash was verified before refreshing provenance. No security behavior changes.
Deployment Notes
No special deployment requirements or migrations.
Additional Notes
No plan departures or unrelated follow-ups. The refresh date records when the snapshot was verified (2026-10-06); validation and commit continued into 2026-10-07 local time. This PR is not merged.