ci: align GitHub Actions with server SHAs, delegate pinning enforcement to native policy#328
Merged
mpartipilo merged 6 commits intomainfrom Apr 21, 2026
Merged
Conversation
Align all uses: refs to the immutable commit SHAs used by weaviate/weaviate. Major versions bumped where necessary: checkout v6, docker/login v4, upload-artifact v7, download-artifact v8, cache v5. Tags preserved as comments. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
Summary - Weaviate C# Client CoverageSummary
CoverageWeaviate.Client - 48.4%
Weaviate.Client.Analyzers - 0%
Weaviate.Client.VectorData - 50.3%
|
GitHub Actions now supports enforcing SHA-pinning at org level (2025-08-15 announcement). The native policy is strictly better: it blocks non-SHA-pinned workflows at run time across every repo, with no per-repo CI step to maintain. Drop: - tools/linter_actions_pinned.sh - the "Lint pinned actions" preflight step in main.yaml The hidden-Unicode linter stays — trojan-source detection is not part of the native policy. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mpartipilo
force-pushed
the
ci/pin-actions-to-server-sha
branch
from
8d0ef57 to
41871fe
Compare
mpartipilo
changed the title
mpartipilo
force-pushed
the
ci/pin-actions-to-server-sha
branch
from
41871fe to
be74d4e
Compare
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
uses:refs in GitHub Actions workflows to the same commit SHAs used byweaviate/weaviate, so this client stays in lockstep with the servertools/linter_actions_pinned.shand its preflight step — GitHub's repo-level "Require actions to be pinned to a full-length commit SHA" policy (shipped 2025-08-15) enforces this at execution time for every workflow, including ones added lateractions/checkout@v5(unpinned tag) intest-on-weaviate-version.ymlintentionally, as a live probe for the native policy once it's enabled on this repoTest plan
@v5ref intest-on-weaviate-version.ymlfails with a policy-violation error (confirming enforcement), then gets re-pinned in a follow-up🤖 Generated with Claude Code