Skip to content

chore(deps): update launchdarkly/gh-actions requirement to contract-tests-v1.3.0 - #132

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/launchdarkly/gh-actions-contract-tests-v1.3.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/launchdarkly/gh-actions-contract-tests-v1.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 20, 2026 •

Copy link
Copy Markdown

Updates the requirements on launchdarkly/gh-actions to permit the latest version.

Release notes

Sourced from launchdarkly/gh-actions's releases.

contract-tests: v1.3.0

1.3.0 (2026-01-02)

Features

  • Control whether or not to run with "-stop-service-at-end" (#73) (59238b0)
Commits

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 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)

Note

Overview
Bumps the contract-tests GitHub Action in CI from contract-tests-v1.1.0 to contract-tests-v1.3.0 (same skips and params; upstream adds optional control over -stop-service-at-end). No other workflow inputs change.

The publish workflow also retags release-secrets and sign-dlls to @contract-tests-v1.3.0 (from release-secrets-v1.2.1 and sign-dlls-v1.0.2). That shares one release tag across three different action paths—worth confirming those directories resolve correctly before relying on a release run.

Reviewed by Cursor Bugbot for commit af351fb. Bugbot is set up for automated code reviews on this repo. Configure here.

…ests-v1.3.0

Updates the requirements on [launchdarkly/gh-actions](https://github.com/launchdarkly/gh-actions) to permit the latest version.
- [Release notes](https://github.com/launchdarkly/gh-actions/releases)
- [Commits](https://github.com/launchdarkly/gh-actions/commits/contract-tests-v1.3.0)

---
updated-dependencies:
- dependency-name: launchdarkly/gh-actions
  dependency-version: 1.3.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 20, 2026 23:19
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 20, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit af351fb. Configure here.

- uses: actions/checkout@v7

- uses: launchdarkly/gh-actions/actions/release-secrets@release-secrets-v1.2.1
- uses: launchdarkly/gh-actions/actions/release-secrets@contract-tests-v1.3.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Wrong tags for unrelated actions

High Severity

Dependabot rewrote release-secrets and sign-dlls to @contract-tests-v1.3.0. Those actions are independently versioned, so the publish job would check out the January contract-tests snapshot instead of release-secrets-v1.2.1 and sign-dlls-v1.0.2, dropping later Node 24 and signing fixes and risking a failed release.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit af351fb. Configure here.

@cursor cursor Bot added the risk:high label Nov 20, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk: high.

Automated risk review (dry run): High

This PR would not be automatically approved. Human approval required.

Why: This changes CI workflow definitions in .github/workflows/ci.yml and .github/workflows/publish.yml, including retagging release-secrets and sign-dlls to @contract-tests-v1.3.0. Cursor Bugbot reported an unresolved high-severity finding on those incorrect action tags, so this cannot be Low or auto-approved.

If you disagree with this review, share this PR in #feedback-agent-approvals or submit a changes-requested review explaining why.

Open in Web View Automation 

Sent by Cursor Approval Agent: Dry-Run PR Approver

@jsonbailey jsonbailey 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.

Do not merge. This PR sets an invalid ref for launchdarkly/gh-actions:

  • release-secrets@contract-tests-v1.3.0: the tag is for a different action
  • sign-dlls@contract-tests-v1.3.0: the tag is for a different action

Dependabot treats all actions in launchdarkly/gh-actions as one dependency, because the tags use a dash between the action name and the version. It then moves every ref to the newest tag in the repo, even when that tag belongs to another action. The fix is in launchdarkly/gh-actions#137.

This branch has not been deployed

No deployments
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 github_actions Pull requests that update GitHub Actions code risk:high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant