Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to OSCAL 1.1.3 #1758

Open
degenaro opened this issue Nov 26, 2024 · 2 comments · Fixed by #1795
Open

Upgrade to OSCAL 1.1.3 #1758

degenaro opened this issue Nov 26, 2024 · 2 comments · Fixed by #1795
Milestone
v3.8.0

Comments

@degenaro
Copy link
Collaborator

Issue description / feature objectives

OSCAL 1.1.3 has been released.

Caveats / Assumptions

Update code base to support new OSCAL release.

Completion Criteria

All test cases pass.
@jpower432 jpower432 mentioned this issue Dec 4, 2024
Open
2 tasks
@butler54
Copy link
Collaborator

butler54 commented Dec 5, 2024

Before we get to OSCAL 1.1.3 can we make sure there are no 'dead' classes kicking around e.g.: https://github.com/oscal-compass/compliance-trestle/blob/9f4919b81017018dbcdc714cf800ee6597e4ea26/trestle/oscal/common.py#L400C1-L404C1

@jpower432 jpower432 added this to the v4.0.0 milestone Dec 9, 2024
@jpower432 jpower432 moved this from New to Ready in Trestle Roadmap Dec 9, 2024
@jpower432 jpower432 linked a pull request Feb 13, 2025 that will close this issue
feat: upgrade to OSCAL 1.1.3 #1795
Merged
11 tasks
@jpower432
Copy link
Member

Closed by #1795

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Trestle Roadmap
Status: Ready
Milestone
v3.8.0
Development

Successfully merging a pull request may close this issue.

feat: upgrade to OSCAL 1.1.3 oscal-compass/compliance-trestle
3 participants
@degenaro @butler54 @jpower432