Skip to content

Update github actions - #7139

Merged
jhrozek merged 1 commit into
mainfrom
renovate/github-actions
Nov 15, 2026
Merged

jhrozek merged 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
anthropics/claude-code-action action patch v1.0.269 → v1.0.276
azure/setup-helm action minor v5.0.1 → v5.1.0
helm uses-with patch v4.3.1 → v4.3.2

Release Notes

anthropics/claude-code-action

v1.0.276

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.275...v1.0.276

v1.0.275

Compare Source

What's Changed
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.274...v1.0.275

v1.0.274

Compare Source

What's Changed
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.273...v1.0.274

v1.0.273: (breaking changes)

Compare Source

What's Changed
⚠️ Breaking changes
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.272...v1.0.273

⚠️ Upgrade notes: new security defaults

This release tightens what a Claude session can do, especially on content from people without write access. Workflows on @v1 get these changes automatically. Most keep working as they are, but check the items below if yours runs tests on outside pull requests, uses later steps after the action, or relies on --allowedTools as a strict list.

Sessions start in auto mode

A safety review now decides tool calls that no allow rule covers. Calls that used to be denied can run if the review passes, so --allowedTools is no longer a strict list. Workflows with a prompt can also edit workspace files without an allow rule.

Opt out: set the earlier mode in claude_args: --permission-mode acceptEdits for @claude mentions, or --permission-mode default for workflows with a prompt.

Sessions keep the earlier defaults if you set allowed_non_write_users, allowed_bots, a custom ANTHROPIC_BASE_URL or path_to_claude_code_executable. The same applies if your settings input is a file path, or sets a base URL or another permission mode.

Code-running commands are denied on outside pull requests

If a pull request's author doesn't have write access, common commands such as npm test and bun install are denied, even if claude_args allows them. The run still succeeds, so check the log for a warning.

Opt out: restrict_untrusted_prs: false. This lets code from that pull request run in a job that holds your workflow's tokens.

Only trusted text and runs start a session
  • Slash commands and the trusted request come only from text the person who triggered the run wrote. Claude still reads a labeled or assigned issue's body for context.
  • Editing or deleting someone else's comment or review no longer starts a run.
  • With prompt and track_progress, label_trigger and assignee_trigger now apply.
  • workflow_run also checks the owner of the fork the run came from.
  • A run started by a bot's activity on a pull request also needs that pull request's author to have write access or be an allowed bot.

Adjust:

  • If your workflow filters labels itself, set label_trigger to your label, or to "" to accept any label.
  • For workflow_run on outside contributions, add those users to allowed_non_write_users and pass github_token.

There's no opt-out for the rest.

A session can't leave anything behind for later steps

GITHUB_ENV, GITHUB_PATH and git config are restored when the session ends, so a session's changes to them no longer reach later steps. Token revocation also ignores ~/.curlrc, including a proxy set there.

Git hooks are also off from before the checkout on pull requests covered by restrict_untrusted_prs, so a push Claude makes on one of those won't upload Git LFS objects.

Adjust: pass values to later steps with GITHUB_OUTPUT or --json-schema. There's no opt-out.

No token in .git/config when allowed_bots is set

These workflows now use the same credential helper as allowed_non_write_users, and it only answers for your GitHub server.

Adjust: a later step that pushes through origin, or fetches from it on a private repository, needs its own credentials: GH_TOKEN, GIT_ASKPASS, a credential saved for the username x-access-token, or its own remote URL. There's no opt-out.

Stricter git commands in @claude runs
  • Commits go through a wrapper that rejects flags outside a short list, including --amend, --no-verify, --author and flags that read a file.
  • Pushes can't be forced and only update the branch the session was set up on: a new branch, or the open pull request's branch.
  • A deny rule for git commit or git push must be in claude_args to cover these wrappers. One in a settings file doesn't.

Opt out: add your own rule in claude_args, such as Bash(git commit:*) or Bash(git push:*). This brings back what the wrappers block for that workflow.

Signed commits from prompt runs go to their own branch

With use_commit_signing, a run on an issue now commits to issue-N. A run on a pull request commits to its branch, or to pr-N if that branch isn't known to be in this repository. They used to reach the default branch or a branch named by a fork.

Opt out: set CLAUDE_BRANCH in the step's env to choose the branch.

v1.0.272

Compare Source

What's Changed

Full Changelog: anthropics/claude-code-action@v1.0.271...v1.0.272

v1.0.271

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.270...v1.0.271

v1.0.270

Compare Source

What's Changed
  • release: push tags with the release deploy key (enables tag-ruleset enforcement) by @​chrnorm in #​1650
New Contributors

Full Changelog: anthropics/claude-code-action@v1.0.269...v1.0.270

azure/setup-helm

v5.1.0

Compare Source

Added
Fixed
Security
Changed
helm/helm (helm)

v4.3.2: Helm v4.3.2

Compare Source

Helm v4.3.2 is a patch release. Users are encouraged to upgrade for the best experience.

The community keeps growing, and we'd love to see you there!

  • Join the discussion in Kubernetes Slack:
    • for questions and just to hang out
    • for discussing PRs, code, and bugs
  • Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom
  • Test, debug, and contribute charts: ArtifactHub/packages
Notable Changes
Installation and Upgrading

Download Helm v4.3.2. The common platform binaries are here:

This release was signed with 208D D36E D5BB 3745 A167 43A4 C7C6 FBB5 B91C 1155 and can be found at @​scottrigby keybase account. Please use the attached signatures for verifying this release using gpg.

The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash.

What's Next
  • 4.3.2 is the next patch releases scheduled for November 11, 2026
  • 4.4.0 is the next minor release scheduled for January 13, 2027. There will be no further Helm 3 minor releases (see https://helm.sh/blog/helm-v3-end-of-life)
Changelog
  • fix(deps): bump golang.org/x/net to v0.62.0 (#​32876) 8346aaa (Sean Schneeweiss)
  • chore(deps): bump github.com/distribution/distribution/v3 (#​32698) 8c92fca (dependabot[bot])
  • fix(deps): bump github.com/klauspost/compress to v1.20.3 (#​32878) 214f6f6 (Sean Schneeweiss)
  • chore(deps): bump the k8s-io group across 1 directory with 7 updates 90d48fc (dependabot[bot])
  • fix(registry): always return a transport Helm can configure (#​32684) 961bddf (ump45nose)
  • docs(cmd): correct list --max and HELM_COLOR help text (#​32807) ddb8be7 (Zain Qureshi)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 14, 2026
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 14, 2026
@github-actions github-actions Bot added the size/XS Extra small PR: < 100 lines changed label Nov 14, 2026
@codecov

codecov Bot commented Nov 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.25%. Comparing base (5f36b56) to head (9bd70a7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7139   +/-   ##
=======================================
  Coverage   81.24%   81.25%           
=======================================
  Files         877      879    +2     
  Lines       89907    89947   +40     
=======================================
+ Hits        73043    73082   +39     
- Misses      16859    16860    +1     
  Partials        5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jhrozek jhrozek left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Checked the diff: action pins and Helm version bumps only, matching the tags upstream. CI is green. Approving.

@jhrozek
jhrozek merged commit 8b7c732 into main Nov 15, 2026
46 checks passed
@jhrozek
jhrozek deleted the renovate/github-actions branch November 15, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file size/XS Extra small PR: < 100 lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant