Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 8, 2025

Bumps getsentry/github-workflows/.github/workflows/updater.yml from 2 to 3.

Release notes

Sourced from getsentry/github-workflows/.github/workflows/updater.yml's releases.

3.0.0

Breaking Changes

  • Updater: The default value for pr-strategy has been changed from create to update. (#124) This change means the updater will now maintain a single PR that gets updated with new dependency versions (instead of creating separate PRs for each version). If you want to preserve the previous behavior of creating separate PRs, explicitly set pr-strategy: create in your workflow:

    - uses: getsentry/github-workflows/updater@v3
      with:
        # ... other inputs ...
        pr-strategy: create  # Add this to preserve previous behavior

    In case you have existing open PRs created with the create strategy, you will need to remove these old branches manually as the new name would be a prefix of the old PRs, which git doesnt' allow.

  • Updater and Danger reusable workflows are now composite actions (#114)

    To update your existing Updater workflows:

    ### Before
      native:
        uses: getsentry/github-workflows/.github/workflows/updater.yml@v2
        with:
          path: scripts/update-sentry-native-ndk.sh
          name: Native SDK
        secrets:
          # If a custom token is used instead, a CI would be triggered on a created PR.
          api-token: ${{ secrets.CI_DEPLOY_KEY }}
    After
    native:
    runs-on: ubuntu-latest
    steps:
    - uses: getsentry/github-workflows/updater@v3
    with:
    path: scripts/update-sentry-native-ndk.sh
    name: Native SDK
    api-token: ${{ secrets.CI_DEPLOY_KEY }}

    To update your existing Danger workflows:

    ### Before
      danger:
        uses: getsentry/github-workflows/.github/workflows/danger.yml@v2
    After
    danger:

... (truncated)

Changelog

Sourced from getsentry/github-workflows/.github/workflows/updater.yml's changelog.

Changelog

Unreleased

Features

  • Danger - Add support for repository-specific dangerfiles (#129)
    • Add extra-dangerfile input parameter to run custom Danger checks alongside shared workflow checks
    • Add extra-install-packages input to install additional apt packages required by custom dangerfiles
    • Custom dangerfiles receive full Danger API access (fail, warn, message, markdown, danger)
    • Enables repositories to extend Danger checks without overwriting shared workflow comments

3.1.0

Features

  • Updater - Add post-update-script input parameter to run custom scripts after dependency updates (#130, #133)
    • Scripts receive original and new version as arguments
    • Support both bash (.sh) and PowerShell (.ps1) scripts
    • Enables workflows like updating lock files, running code generators, or modifying configuration files
  • Updater - Add SSH key support and comprehensive authentication validation (#134)
    • Add ssh-key input parameter for deploy key authentication
    • Support using both ssh-key (for git) and api-token (for GitHub API) together
    • Add detailed token validation with actionable error messages
    • Detect common token issues: expiration, whitespace, SSH keys in wrong input, missing scopes
    • Validate SSH key format when provided

Fixes

  • Updater - Fix boolean input handling for changelog-entry parameter and add input validation (#127)
  • Updater - Fix cryptic authentication errors with better validation and error messages (#134, closes #128)

Dependencies

3.0.0

Breaking Changes

  • Updater: The default value for pr-strategy has been changed from create to update. (#124) This change means the updater will now maintain a single PR that gets updated with new dependency versions (instead of creating separate PRs for each version). If you want to preserve the previous behavior of creating separate PRs, explicitly set pr-strategy: create in your workflow:

    - uses: getsentry/github-workflows/updater@v3
      with:
        # ... other inputs ...

... (truncated)

Commits
  • 13be9be release: 3.1.0
  • 0d0d99a feat(updater): Add SSH key support and comprehensive authentication validatio...
  • 6272a50 chore(deps): update Danger JS to v13.0.4 (#132)
  • 71d223e fix(updater): Pass OriginalTag to post-update script on second run (#133)
  • 0bd595f chore: Rename workflow to 'Update dependencies'
  • 1c10977 chore: Use updater action to manage Danger JS version (#131)
  • 3182dd4 feat(updater): Add post-update-script support (#130)
  • 15e4b10 fix: Handle boolean inputs correctly and validate supported values (#127)
  • c6471d1 Merge branch 'release/3.0.0'
  • 342f5e2 release: 3.0.0
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…r.yml

Bumps [getsentry/github-workflows/.github/workflows/updater.yml](https://github.com/getsentry/github-workflows) from 2 to 3.
- [Release notes](https://github.com/getsentry/github-workflows/releases)
- [Changelog](https://github.com/getsentry/github-workflows/blob/main/CHANGELOG.md)
- [Commits](getsentry/github-workflows@v2...v3)

---
updated-dependencies:
- dependency-name: getsentry/github-workflows/.github/workflows/updater.yml
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies github_actions Pull requests that update GitHub Actions code labels Dec 8, 2025
@dependabot dependabot bot requested review from buenaflor and romtsn as code owners December 8, 2025 03:15
@dependabot dependabot bot added dependencies github_actions Pull requests that update GitHub Actions code labels Dec 8, 2025
Comment on lines 9 to 15

jobs:
cocoa:
uses: getsentry/github-workflows/.github/workflows/updater.yml@v2
uses: getsentry/github-workflows/.github/workflows/updater.yml@v3
with:
path: scripts/update-cocoa.sh
name: Cocoa SDK
Copy link

Choose a reason for hiding this comment

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

Bug: The updater@v3 action is incorrectly called at the job level, causing workflow execution to fail.
Severity: CRITICAL | Confidence: High

🔍 Detailed Analysis

The workflow uses uses: getsentry/github-workflows/.github/workflows/updater.yml@v3 at the job level, which is incorrect for v3 of the updater action. v3 is a Composite Action and must be called within a steps block. The current syntax is for reusable workflows, which v3 is not. This structural mismatch will cause GitHub Actions to fail execution for both cocoa and java jobs.

💡 Suggested Fix

Refactor the cocoa and java jobs to include a runs-on property at the job level and a steps block, calling uses: getsentry/github-workflows/updater@v3 within a step.

🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/update-deps.yml#L9-L15

Potential issue: The workflow uses `uses:
getsentry/github-workflows/.github/workflows/updater.yml@v3` at the job level, which is
incorrect for `v3` of the `updater` action. `v3` is a Composite Action and must be
called within a `steps` block. The current syntax is for reusable workflows, which `v3`
is not. This structural mismatch will cause GitHub Actions to fail execution for both
`cocoa` and `java` jobs.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 6029038

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant