🔄 Preview: Sync 2.2.2 RNs.mdx - #2786
Draft
probelabs[bot] wants to merge 492 commits into
Draft
probelabs / Visor: architecture
failed
Aug 27, 2026 in 36s
🚨 Check Failed
architecture check failed because fail_if condition was met.
Details
📊 Summary
- Total Issues: 3
- Error Issues: 3
🔍 Failure Condition Results
Failed Conditions
- global_fail_if: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
- Severity: ❌ error
Issues by Category
Architecture (2)
- ❌ developer-support/release-notes/overview.mdx:42 - The release metadata in
overview.mdxis inconsistent with the new release notes. While the version number for Tyk Sync was updated to2.2.2, the associated release date"date": "21/05/2026"was not updated. This creates a discrepancy between the summary metadata and the detailed release notes, and will display incorrect information to users. This points to a potential weakness in the content architecture, where related data in different files can easily fall out of sync. - ❌ developer-support/release-notes/sync.mdx:30 - The release notes for version 2.2.2 contain a placeholder release date:
xx August 2026. Publishing documentation with placeholder content is an architectural process failure. The content authoring and review workflow should prevent incomplete information from being merged.
Logic (1)
- ❌ system:0 - Global failure condition met: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check failure on line 42 in developer-support/release-notes/overview.mdx
probelabs / Visor: architecture
architecture Issue
The release metadata in `overview.mdx` is inconsistent with the new release notes. While the version number for Tyk Sync was updated to `2.2.2`, the associated release date `"date": "21/05/2026"` was not updated. This creates a discrepancy between the summary metadata and the detailed release notes, and will display incorrect information to users. This points to a potential weakness in the content architecture, where related data in different files can easily fall out of sync.
Raw output
Update the release date to match the actual release date for version 2.2.2. To prevent this in the future, consider architectural improvements like a single source of truth for release metadata or automated validation checks to ensure consistency between related documentation files.
Check failure on line 30 in developer-support/release-notes/sync.mdx
probelabs / Visor: architecture
architecture Issue
The release notes for version 2.2.2 contain a placeholder release date: `xx August 2026`. Publishing documentation with placeholder content is an architectural process failure. The content authoring and review workflow should prevent incomplete information from being merged.
Raw output
Replace the placeholder `xx` with the correct day of the release. Ensure the date is consistent with the date used in `developer-support/release-notes/overview.mdx`.
Loading