chore(deps): update pypa/gh-action-pypi-publish digest to cef2210#363
chore(deps): update pypa/gh-action-pypi-publish digest to cef2210#363renovate[bot] wants to merge 1 commit into
Conversation
WalkthroughWalkthroughUpdated the pinned commit SHA for the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #363 +/- ##
=======================================
Coverage 84.35% 84.35%
=======================================
Files 153 153
Lines 7996 7996
Branches 2163 2163
=======================================
Hits 6745 6745
Misses 1250 1250
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
676a24a to
8f64b4d
Compare
cc9f68d to
f9f6d24
Compare
3f74138 to
5b53809
Compare
99991d4 to
decb330
Compare
decb330 to
1579836
Compare
dec790e to
d434058
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/cd-pypi-cli.yml:
- Line 46: The Setup Bun action step (uses:
oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6) is incorrectly
attempting to use a non-existent `cache` input; change the step to pass the
correct input by adding `with: no-cache: true` to the "Setup Bun" step so Bun
caching is disabled (use the `no-cache` input rather than `cache`).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a23aa126-1262-4adf-8a61-1c8e4f17c8f1
📒 Files selected for processing (1)
.github/workflows/cd-pypi-cli.yml
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/cd-pypi-cli.yml:
- Line 46: The Setup Bun action step (uses:
oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6) is incorrectly
attempting to use a non-existent `cache` input; change the step to pass the
correct input by adding `with: no-cache: true` to the "Setup Bun" step so Bun
caching is disabled (use the `no-cache` input rather than `cache`).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a23aa126-1262-4adf-8a61-1c8e4f17c8f1
📒 Files selected for processing (1)
.github/workflows/cd-pypi-cli.yml
🛑 Comments failed to post (1)
.github/workflows/cd-pypi-cli.yml (1)
46-46:
⚠️ Potential issue | 🟠 Major | ⚡ Quick win🧩 Analysis chain
🏁 Script executed:
#!/bin/bash # Verify setup-bun supports cache input and its default in the pinned commit. set -euo pipefail curl -fsSL https://raw.githubusercontent.com/oven-sh/setup-bun/0c5077e51419868618aeaa5fe8019c62421857d6/action.yml \ | sed -n '1,220p' # Find all setup-bun uses and whether cache is explicitly configured. rg -n -C3 'uses:\s*oven-sh/setup-bun@' .github/workflowsRepository: deepnote/deepnote
Length of output: 3070
Disable Bun caching at Line 46 using
no-cache(notcache)
oven-sh/setup-bun@...(pinned v2) exposesno-cache(default:false); there is nocacheinput. Setwith: no-cache: trueon theSetup Bunstep.Suggested fix
- name: Setup Bun uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # v2 with: no-cache: true🧰 Tools
🪛 zizmor (1.25.2)
[error] 46-46: runtime artifacts potentially vulnerable to a cache poisoning attack (cache-poisoning): enables caching by default
(cache-poisoning)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/cd-pypi-cli.yml at line 46, The Setup Bun action step (uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6) is incorrectly attempting to use a non-existent `cache` input; change the step to pass the correct input by adding `with: no-cache: true` to the "Setup Bun" step so Bun caching is disabled (use the `no-cache` input rather than `cache`).
d434058 to
ca71123
Compare
8a30c0d to
257d345
Compare
1fce866 to
49e605f
Compare
49e605f to
8792d21
Compare
This PR contains the following updates:
ed0c539→cef2210Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.