[codex] Release machine inventory updates and narrow CI branch triggers#131
Merged
Merged
Conversation
jwill824
marked this pull request as ready for review
June 21, 2026 00:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
feat:commit so semantic-release creates a minor release for the already-merged machine inventory/provenance work.mainonly, while keeping PR checks formain.Why
The release pipeline now authenticates successfully, but semantic-release saw only non-release squash commit titles after
v1.7.0and correctly reported no relevant changes. The emptyfeat:commit gives semantic-release an explicit release signal.The CI workflow previously ran on every branch push and again on PRs. This keeps PR validation and adds one post-merge run on
mainwithout branch-push duplicates.Validation
git diff --checkAnalysis of 10 commits complete: no release, confirming this is a commit-analysis issue rather than an auth/build failure.