Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your changes status has failed because you have indirect coverage changes. Learn more about Unexpected Coverage Changes and reasons for indirect coverage changes. Additional details and impacted files@@ Coverage Diff @@
## main #2085 +/- ##
==========================================
- Coverage 83.62% 83.59% -0.04%
==========================================
Files 184 184
Lines 13627 13632 +5
Branches 1270 1271 +1
==========================================
Hits 11395 11395
- Misses 2059 2064 +5
Partials 173 173
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
| # included as forward-looking support. | ||
| - platform: "2023" | ||
| cxx-standard: 17 | ||
| image: "aswf/ci-otio:2023@sha256:888156204e68f3ced0ff277157423852c9330f0eed48419361a67fbf5ab48a53" |
There was a problem hiding this comment.
I acknowledge that this might be overkill, so I'll let whomever reviews this decide if it's really worth it or not.
Assisted-by: OpenAI Codex / GPT-6 Signed-off-by: Jeff Hodges <jeff@jeffhq.com>
d22a7e0 to
aab35c7
Compare
The Slack announcement uses release context and remote actions only. The checkout ran in a separate job and provided no files or outputs to the announcement. Assisted-by: OpenAI Codex / GPT-6 Signed-off-by: Jeff Hodges <jeff@jeffhq.com>
Pass the published release body through the existing Markdown-to-Slack conversion so the notification contains the notes as well as a link to the release. Assisted-by: OpenAI Codex / GPT-6 Signed-off-by: Jeff Hodges <jeff@jeffhq.com>
Summary
Follow up on a maintainer security audit by narrowing GitHub Actions token permissions and pinning direct build inputs.
Changes
::set-outputcommand in the release-preview workflow withGITHUB_OUTPUT.actions: readfor artifact downloads, and the specific write/read permissions needed for release preview. The release announcement job receives no repository token permissions.load-repocheckout job andneeds: [load-repo]dependency from release publishing. The Slack announcement uses no files or outputs from that separate job.The build-system pins use a setuptools release that supports Python 3.9 and CMake 3.31 to avoid the known Windows CMake 4/vcpkg ZLIB issue. Direct pins will need regular dependency updates.
Validation
actionlint -shellcheck= -color=falsepassed; the changed release and VFX workflows also passed fullactionlint.actionlint .github/workflows/release-publish.ymlpassed after the two release-announcement follow-up changes.make lintpassed.make testran 487 Python tests: two skipped, one failure, and one error. The version-map generator failed because the local CMake-installed package lacked__version__;UnknownSchema.dataraisedbad any cast. Neither failing test exercises a changed workflow. No new unit tests were added for these configuration changes.Assisted-by: OpenAI Codex / GPT-6 Daybreak (cyber-security model)