Skip to content

fix(ci): resolve all zizmor findings and add zizmor pre-commit checks#257

Merged
rapids-bot[bot] merged 8 commits into
rapidsai:mainfrom
gforsyth:securitize
May 6, 2026
Merged

fix(ci): resolve all zizmor findings and add zizmor pre-commit checks#257
rapids-bot[bot] merged 8 commits into
rapidsai:mainfrom
gforsyth:securitize

Conversation

@gforsyth
Copy link
Copy Markdown
Contributor

@gforsyth gforsyth commented May 6, 2026

Similar to upstream changes in shared-workflows, this PR cleans up and annotates all of the workflows and adds the zizmor linter to make sure changes are checked.

Part of rapidsai/build-planning#275

@gforsyth gforsyth requested a review from a team as a code owner May 6, 2026 15:56
@gforsyth gforsyth requested review from KyleFromNVIDIA and removed request for a team May 6, 2026 15:56
@gforsyth gforsyth added improvement Improves an existing functionality non-breaking Introduces a non-breaking change labels May 6, 2026
Copy link
Copy Markdown
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Gil! 🙏

Had one nit below. Otherwise LGTM

Comment thread .github/zizmor.yml Outdated
Comment on lines +32 to +41
NEXT_PATCH_VERSION=$(echo "${LAST_TAG}" | awk -F. -v OFS=. '{$NF += 1 ; print}')
echo "NEXT_PATCH_VERSION=${NEXT_PATCH_VERSION}" >> "${GITHUB_ENV}"
- name: Release
uses: softprops/action-gh-release@v1
with:
files: ${{ env.RELEASE_FILE_NAME }}
tag_name: ${{ env.NEXT_PATCH_VERSION }}
env:
GH_TOKEN: ${{ github.token }}
run: |
gh release create "${NEXT_PATCH_VERSION}" "${RELEASE_FILE_NAME}" \
--target "${GITHUB_SHA}" \
--title "${NEXT_PATCH_VERSION}" \
--notes ""
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This gets rid of a third-party action in favor of gh functionality -- it will require a merge (of this PR) to test that the release happens as expected.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Gil! 🙏

Agree this is a nice improvement

Do we need any other permissions for this to work?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think github.token is sufficient? But we'll find out!

Co-authored-by: jakirkham <jakirkham@gmail.com>
Copy link
Copy Markdown
Member

@jameslamb jameslamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very happy to see one less third-party action dependency!

Comment on lines +35 to +41
env:
GH_TOKEN: ${{ github.token }}
run: |
gh release create "${NEXT_PATCH_VERSION}" "${RELEASE_FILE_NAME}" \
--target "${GITHUB_SHA}" \
--title "${NEXT_PATCH_VERSION}" \
--notes ""
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Yeah if this gh CLI call does the same thing as that third-party action, it's definitely preferable.

@gforsyth
Copy link
Copy Markdown
Contributor Author

gforsyth commented May 6, 2026

Ok, going to merge this, then make sure that a new release gets cut

@gforsyth
Copy link
Copy Markdown
Contributor Author

gforsyth commented May 6, 2026

/merge

@rapids-bot rapids-bot Bot merged commit 7dde9ce into rapidsai:main May 6, 2026
3 checks passed
@gforsyth
Copy link
Copy Markdown
Contributor Author

gforsyth commented May 6, 2026

BOOM: https://github.com/rapidsai/gha-tools/releases/tag/v0.0.201

(that's the good kind of BOOM)

@gforsyth gforsyth deleted the securitize branch May 6, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants