Skip to content

chore(deps): bump github.com/aws/aws-sdk-go-v2/credentials from 1.19.7 to 1.19.9#7

Closed
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/go_modules/develop/github.com/aws/aws-sdk-go-v2/credentials-1.19.9
Closed

chore(deps): bump github.com/aws/aws-sdk-go-v2/credentials from 1.19.7 to 1.19.9#7
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/go_modules/develop/github.com/aws/aws-sdk-go-v2/credentials-1.19.9

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Feb 23, 2026

Bumps github.com/aws/aws-sdk-go-v2/credentials from 1.19.7 to 1.19.9.

Commits

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

Bumps [github.com/aws/aws-sdk-go-v2/credentials](https://github.com/aws/aws-sdk-go-v2) from 1.19.7 to 1.19.9.
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/main/changelog-template.json)
- [Commits](aws/aws-sdk-go-v2@service/m2/v1.19.7...service/m2/v1.19.9)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go-v2/credentials
  dependency-version: 1.19.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@lerian-studio
Copy link
Copy Markdown
Contributor

Consider updating CHANGELOG.md to document this change. If this change doesn't need a changelog entry, add the skip-changelog label.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 23, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Feb 26, 2026

Looks like github.com/aws/aws-sdk-go-v2/credentials is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Feb 26, 2026
@dependabot dependabot Bot deleted the dependabot/go_modules/develop/github.com/aws/aws-sdk-go-v2/credentials-1.19.9 branch February 26, 2026 19:44
jgbr1el93 added a commit that referenced this pull request May 15, 2026
Addresses 6 actionable findings from the CodeRabbit Cloud review of the
re-submitted security fix. All are quality refinements on artifacts we
authored; no behavior change to the security contract itself.

Code fixes:

- fuzz test buildActorMapping (#5): validate UTF-8 only on fields the
  caller marks as present. The previous guard rejected the entire
  mapping when an absent field happened to carry invalid bytes — those
  bytes are never read in the absent branch, so the rejection only
  shrank the valid input space without protecting any assertion.

- integration test idempotency assertions (#6): switch from
  .Unix() epoch-seconds comparison to time.Time.Equal(). Sub-second
  drift was previously absorbed by the seconds-precision rounding; the
  tighter comparison now surfaces any spurious updated_at write
  introduced by a future regression. Applied at both call sites in the
  AC2 and AC8-identical-payload tests.

- chaos harness fatal message (#10): the t.Fatalf text on the
  testLockHeld CAS used to say "called twice on the same test", but the
  CAS is harness-scoped, so any second acquirer (including a future
  parallel test if the suite is ever de-serialized) would land in the
  same branch. Rephrase the message to reference the chaos suite
  serial-execution invariant and the docstring that explains it.
  Applied to both ResetDatabase and LockHarnessForTest.

Documentation:

- ActorMappingRepository.Upsert contract (#7): the docstring said
  identity fields must match "exactly", but the adapter helpers
  (stringPtrEqual / actorMappingPIIDiffers) intentionally treat
  nil-pointer and empty-string as equivalent because the DB stores
  NULL for both. Document the equivalence explicitly in the contract
  so future maintainers don't read "exactly" as byte-strict including
  nil-vs-empty.

- Task spec PoC step 1 (#4): the pentest reproduction in
  docs/tasks/fix-actor-mapping-pseudonymization-bypass.md said
  "POST /v1/governance/actor-mappings/{ID} creates mapping". The
  actual route is PUT — there is no POST create endpoint. Corrected
  with a clarifying parenthetical.

- Cycle state metrics (#1): docs/ring:dev-cycle/current-cycle.json
  had accumulated_metrics.review_iterations: 0 despite the cycle
  documenting Gate 8 iteration 1 plus 4 MEDIUM findings resolved.
  Updated to review_iterations: 1 and populated issues_by_severity
  with the actual counts (4 MEDIUM, 22 LOW) so the state file
  truthfully audits the cycle.

Findings #2, #3, #8, #9 are tracked as deferred with replies on the
PR threads — they cover policy decisions (pre-launch patch posture),
process documentation that was already conscious, sibling-method
consistency, and an intentional defensive check.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant