Skip to content

Conversation

@sujata-m
Copy link
Collaborator

@sujata-m sujata-m commented Jan 9, 2026

Dev Board Ticket

N/A

Changes

Add compatibility/support for OSW 0.3 in the TDEI Python OSW formatter so the library can parse and/or produce OSW files conforming to the OSW 0.3 specification. Likely changes include parser/serializer updates, schema handling, tests, and possibly CI or docs updates. The [Prod] tag indicates this targets a production release.

Why this matters

  • Enables downstream consumers to migrate to OSW 0.3 without breaking formatting or validation.
  • Ensures the formatter stays current with the OSW spec and avoids interoperability issues.
  • May require a library version bump and release notes to guide users.

Potential impacts & compatibility notes

  • Backwards compatibility: verify whether OSW 0.3 introduces breaking changes vs earlier OSW versions.
  • Dependencies: check for new or updated dependencies and their impact on CI and packaging.
  • Versioning & release notes: ensure semantic version bump and clear migration guidance if needed.

Recommended review checklist

  • Confirm parser updates correctly handle any new/renamed fields or structural changes in OSW 0.3.
  • Verify serializer/formatter output conforms to OSW 0.3 expectations.
  • Check unit/integration tests were added/updated for OSW 0.3 scenarios and that they pass.
  • Inspect CI configuration for any necessary changes; confirm CI passes.
  • Ensure docs/changelog are updated with migration instructions.
  • Run tests locally: python -m pytest (or the repository’s test command).
  • Validate end-to-end with a sample OSW 0.3 file and compare outputs against expected schema.

Testing

  • TDEI Portal

@sujata-m sujata-m merged commit e5d6d8c into main Jan 9, 2026
6 checks passed
@sujata-m sujata-m deployed to Production January 9, 2026 08:05 — with GitHub Actions Active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants