Check `zizmor` 1.32

Open
#66 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
53/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python
Domain
devops, security

Research direction

Start with the linked zizmor 1.32 release notes, then locate the repository's existing zizmor configuration and GitHub Actions workflow. Check whether this version can be adopted and lock files enabled; the work is done when the repository uses the update and lock-file support, or the investigation establishes why it cannot.

Written by the indexing model from the issue text.

Description

zizmor released 1.32 which adds support for lock files. We should look and see if we can update to this version and use the lock files.

https://docs.zizmor.sh/release-notes/#1320

Dominant language
Python
Stars
4
Forks
8
Avg merge
21h 34m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from render-engine/render-engine-cli

All issues in render-engine/render-engine-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.