Repository navigation
Conversation
added 4 commits
October 4, 2026 23:09
- remove the 'watch: started' trigger (runs the scan when someone stars the repo - pointless and noisy) - pin aquasecurity/[email protected] instead of the floating @master (supply-chain and reproducibility) - bump actions/checkout v3 -> v4 (Node 20 deprecation) Note: the workflow is currently in 'disabled_inactivity' state (GitHub auto-disabled the cron schedule after repo inactivity), which also stops its push/pull_request triggers from firing - it has not run on push or PR at all, only a handful of weekly cron runs that last ran in January 2026. Pushing this change does NOT re-enable it: an admin must re-enable the workflow in the Actions tab (or via the API) for scanning to actually resume. Signed-off-by: pirog-spb <[email protected]>
The robot-test workflow fired a phantom run with zero jobs on every push to main (marked failed) while nothing in the repository calls it: a leftover trigger registration from before it became a workflow_call reusable workflow. Renaming the file path re-registers the workflow and stops the phantom runs. While at it, fix the reusable-workflow bugs that made the test unusable even when called: - github.event.inputs.* does not exist for workflow_call; use inputs.* (the values were always substituted empty) - the job remapped kube_config from secrets.KUBE_CONFIG_DEV instead of the caller-provided secrets.kube_config - replace the unmaintained BSFishy/pip-action with a plain pip install - bump actions/checkout v3 -> v4 and actions/setup-python v1 -> v5 (Node 20 deprecation), add timeout-minutes and upload robot results as an artifact instead of leaving them on the runner Signed-off-by: pirog-spb <[email protected]>
- build.yml: checkout v3 -> v4, docker/metadata-action v4 -> v5 - deploy.yml: checkout v3 -> v4, azure/setup-helm v3 -> v4 (helm version itself stays pinned at v3.11.1 on purpose - bumping the deployed helm version is a separate, riskier change) - loadtest.yml: setup-python v1 -> v5 with a pinned python-version (v1 is ancient and targets the deprecated Node.js 20 runtime) Removes the remaining Node.js 20 deprecation warnings and unpinned third-party action references. Signed-off-by: pirog-spb <[email protected]>
The repository tags are prefixed with 'v' (refs/tags/v0.36.0 exists, 0.36.0 does not), so the previous pin failed to resolve: Error: Unable to resolve action `aquasecurity/[email protected]`, unable to find version `0.36.0` Signed-off-by: pirog-spb <[email protected]>
This was referenced Oct 4, 2026
pirog-spb
added a commit
that referenced
this pull request
Oct 31, 2026
Signed-off-by: pirog-spb <[email protected]> (cherry picked from commit ebf1453) Signed-off-by: pirog-spb <[email protected]>
pirog-spb
added a commit
that referenced
this pull request
Oct 31, 2026
Signed-off-by: pirog-spb <[email protected]> (cherry picked from commit ebf1453) Signed-off-by: pirog-spb <[email protected]>
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
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.
No description provided.