Update dependency compliance-trestle to v3.12.0

[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

Package	Change	Age	Confidence
compliance-trestle	==3.11.0 -> ==3.12.0

---

Release Notes

oscal-compass/compliance-trestle (compliance-trestle)

v3.12.0

Compare Source

Bug Fixes

• Add missing optional fields to Parameter and Property constructors
  (#​2049,
  c1bf661)

• Ignore synk error for 60 days
  (#​2065,
  0a8ad53)

• Latest pip-tools fails with pip 26.0
  (#​2079,
  4fac1eb)

• Lint errors (#​2051,
  67a50e2)

• Mypy generic oscal control interface
  (#​2049,
  c1bf661)

• Resolve mypy type error in base_markdown_node.py
  (#​2040,
  e7de1d3)

• Resolve mypy type errors in generators, model_utils, and base_markdown_node
  (#​2040,
  e7de1d3)

• Resolve mypy type errors in generators.py
  (#​2040,
  e7de1d3)

• Resolve mypy type errors in model_utils.py
  (#​2040,
  e7de1d3)

• Serialize docs update (#​2041,
  0158df2)

• Snyk flags error for orjson -> 60 days grace period
  (#​2065,
  0a8ad53)

• Trivial update (#​2065,
  0a8ad53)

• deps: Bump actions/cache from 4.3.0 to 5.0.2
  (#​2045,
  05da505)

• deps: Bump actions/cache from 4.3.0 to 5.0.3
  (#​2078,
  593bb9d)

• deps: Bump actions/checkout from 6.0.1 to 6.0.2
  (#​2071,
  3f7bbc1)

• deps: Bump actions/checkout from 6.0.1 to 6.0.2
  (#​2057,
  8d5d3ee)

• deps: Bump actions/download-artifact from 6.0.0 to 7.0.0
  (#​2046,
  50e471f)

• deps: Bump actions/setup-python from 6.1.0 to 6.2.0
  (#​2068,
  1e2e7ea)

• deps: Bump actions/setup-python from 6.1.0 to 6.2.0
  (#​2054,
  a1dbef4)

• deps: Bump actions/upload-artifact from 5.0.0 to 6.0.0
  (#​2043,
  0e72606)

• deps: Bump cryptography from 46.0.3 to 46.0.4
  (#​2069,
  fd40f56)

• deps: Bump cryptography from 46.0.4 to 46.0.5
  (#​2082,
  dae460a)

• deps: Bump github/codeql-action from 4.31.10 to 4.31.11
  (#​2056,
  6d4bc0c)

• deps: Bump github/codeql-action from 4.31.11 to 4.32.0
  (#​2070,
  dac5dc0)

• deps: Bump github/codeql-action from 4.31.9 to 4.31.10
  (#​2044,
  9e16579)

• deps: Bump python-semantic-release/python-semantic-release
  (#​2042,
  a147827)

Chores

• Apply automated formatting to modified files
  (#​2040,
  e7de1d3)

• Progressively eliminate lint exceptions (Phase 1)
  (#​2053,
  0d7a953)

• Progressively eliminate lint exceptions (Phase 2)
  (#​2058,
  d4fd6cf)

• Progressively eliminate lint exceptions (Phase 3)
  (#​2059,
  e2de2dd)

• Progressively eliminate lint exceptions (Phase 4)
  (#​2060,
  cbecb5d)

• Progressively eliminate lint exceptions (Phase 5)
  (#​2067,
  c68a5b3)

Documentation

• Update CLI tutorial to use NIST 800-53 rev5
  (#​1984,
  0bd3e28)

Features

• Add a codegen test (#​2041,
  0158df2)

• Pythons supported 3.10-3.13
  (#​2051,
  67a50e2)

• Update NIST 800-53 rev5 CSV/xlsx tasks and tests
  (#​1984,
  0bd3e28)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.