Repository navigation
chore: Bump launchdarkly/gh-actions from verify-hello-app-v2.0.2 to 2.0.1 - #39
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [launchdarkly/gh-actions](https://github.com/launchdarkly/gh-actions) from verify-hello-app-v2.0.2 to 2.0.1. This release includes the previously tagged commit. - [Release notes](https://github.com/launchdarkly/gh-actions/releases) - [Commits](launchdarkly/gh-actions@verify-hello-app-v2.0.2...verify-hello-app-v2.0.1) --- updated-dependencies: - dependency-name: launchdarkly/gh-actions dependency-version: 2.0.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ 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 95b7a47. Configure here.
| run: poetry install | ||
|
|
||
| - uses: launchdarkly/gh-actions/actions/verify-hello-app@verify-hello-app-v2.0.2 | ||
| - uses: launchdarkly/gh-actions/actions/verify-hello-app@verify-hello-app-v2.0.1 |
There was a problem hiding this comment.
Action version incorrectly downgraded
High Severity
The workflow pin moves verify-hello-app from v2.0.2 to v2.0.1, which is an older tag, not a newer one. v2.0.2 (Nov 2026) updated the action to Node.js 24; v2.0.1 is from Aug 2024. Merging this reverts that update and leaves CI on a stale action.
Reviewed by Cursor Bugbot for commit 95b7a47. Configure here.
| run: poetry install | ||
|
|
||
| - uses: launchdarkly/gh-actions/actions/verify-hello-app@verify-hello-app-v2.0.2 | ||
| - uses: launchdarkly/gh-actions/actions/verify-hello-app@verify-hello-app-v2.0.1 |
There was a problem hiding this comment.
🔒 Agentic Security Review
Severity: CRITICAL
Description: The CI downgrade from verify-hello-app-v2.0.2 to verify-hello-app-v2.0.1 selects release-secrets v1.2.0, whose AWS credential step is aws-actions/configure-aws-credentials@v4. That tag is an annotated floating ref ("This tag will always track the latest v4 release") and currently points at 7474bc4690e29a8392af63c5b98e7449536d5c3a, not the v6 commit e7f100cf4c008499ea8adda475de1042d6975c7b pinned by release-secrets v1.2.1. The build-and-run job has id-token: write and passes vars.AWS_ROLE_ARN into that step with audience https://github.com/launchdarkly, so whoever next moves v4 executes their code in this job and receives the OIDC token and role ARN.
Impact: This PR adds a new public-artifact trust for the step that mints the GitHub OIDC token and assumes vars.AWS_ROLE_ARN. v2.0.2 kept that step on a commit SHA, so a later move of aws-actions/configure-aws-credentials v4 could not change it. v2.0.1 resolves the credential action at runtime, and the daily schedule plus pull_request runs will execute the new target without another edit to this repo. The same job is already able to assume that role and read the hello-app SSM parameters, including /sdk/common/hello-apps/server-key into LAUNCHDARKLY_SDK_KEY. A moved v4 tag therefore gets the workflow's AWS role credentials and the SDK key. The outer verify-hello-app tag was already controlled by launchdarkly/gh-actions; v4 is a separate upstream publisher that the previous SHA pin did not trust.
Remediation: Revert the workflow pin to launchdarkly/gh-actions/actions/verify-hello-app@verify-hello-app-v2.0.2 so the job keeps release-secrets v1.2.1 and the credential step stays on commit e7f100cf4c008499ea8adda475de1042d6975c7b. If a newer verify-hello-app is required, use one whose nested release-secrets action pins aws-actions/configure-aws-credentials to a reviewed full commit SHA, not the moving v4 tag.




Bumps launchdarkly/gh-actions from verify-hello-app-v2.0.2 to 2.0.1. This release includes the previously tagged commit.
Commits
485c862chore(main): release verify-hello-app 2.0.1 (#39)a1b75f0fix: Bump release-secrets version to avoid node16 dependency (#37)bbbbbdachore(main): release release-secrets 1.2.0 (#36)0921295feat: Update to use configure-aws-credential v4. (#35)0b3ff8fchore(main): release contract-tests 1.0.2 (#33)28cf0d3fix: contract test should download v2 script (#32)03d0c71chore(main): release verify-hello-app 2.0.0 (#31)c5f14e2feat!: rename environment variables passed to hello apps (#29)f9d7025fix!: Remove the legacy success message (#30)f571087ci: add release-please support (#22)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Overview
CI now pins
launchdarkly/gh-actionsverify-hello-appatverify-hello-app-v2.0.1instead ofv2.0.2.The build-and-run job still runs the same step (
use_server_key, AWS role,poetry run python main.py); only the reusable action ref changes.Reviewed by Cursor Bugbot for commit 95b7a47. Bugbot is set up for automated code reviews on this repo. Configure here.