Skip to content

chore(deps): bump github.com/stretchr/testify from 1.10.0 to 1.11.0 - #116

Merged
unclesp1d3r merged 1 commit into
mainfrom
dependabot/go_modules/github.com/stretchr/testify-1.11.0
Aug 30, 2025
Merged

chore(deps): bump github.com/stretchr/testify from 1.10.0 to 1.11.0#116
unclesp1d3r merged 1 commit into
mainfrom
dependabot/go_modules/github.com/stretchr/testify-1.11.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 25, 2025

Copy link
Copy Markdown
Contributor

Bumps github.com/stretchr/testify from 1.10.0 to 1.11.0.

Release notes

Sourced from github.com/stretchr/testify's releases.

v1.11.0

What's Changed

Functional Changes

v1.11.0 Includes a number of performance improvements.

Fixes

Documentation, Build & CI

... (truncated)

Commits
  • b7801fb Merge pull request #1778 from stretchr/dependabot/github_actions/actions/chec...
  • 69831f3 build(deps): bump actions/checkout from 4 to 5
  • a53be35 Improve captureTestingT helper
  • aafb604 mock: improve formatting of error message
  • 7218e03 improve error msg
  • 929a212 Merge pull request #1758 from stretchr/dolmen/suite-faster-method-filtering
  • bc7459e suite: faster filtering of methods (-testify.m)
  • 7d37b5c suite: refactor methodFilter
  • c58bc90 Merge pull request #1764 from stretchr/dolmen/suite-refactor-stats-for-readab...
  • 87101a6 suite.Run: refactor handling of stats
  • 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)

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.10.0 to 1.11.0.
- [Release notes](https://github.com/stretchr/testify/releases)
- [Commits](stretchr/testify@v1.10.0...v1.11.0)

---
updated-dependencies:
- dependency-name: github.com/stretchr/testify
  dependency-version: 1.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Aug 25, 2025
@dependabot
dependabot Bot requested a review from unclesp1d3r as a code owner August 25, 2025 23:49
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Aug 25, 2025
@coderabbitai

coderabbitai Bot commented Aug 25, 2025

Copy link
Copy Markdown
Contributor

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.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Member
  • @dependabot squash and merge

@unclesp1d3r
unclesp1d3r merged commit 714c1c6 into main Aug 30, 2025
12 of 13 checks passed
@unclesp1d3r
unclesp1d3r deleted the dependabot/go_modules/github.com/stretchr/testify-1.11.0 branch August 30, 2025 02:42
unclesp1d3r added a commit that referenced this pull request Apr 19, 2026
…audit, pre-push hook

- Add .github/workflows/security.yml (govulncheck, CodeQL Go analyze,
  Trivy filesystem scan). SARIF uploaded to code scanning. Weekly
  schedule plus on-push and PR.
- Correct SECURITY.md to match reality (drop false Grype/Snyk claims,
  explicitly name govulncheck/CodeQL/Trivy/Scorecard/Dependabot).
- Inventory 9 go.mod pseudo-version dependencies with header block and
  inline rationale per entry. All are upstream-never-tagged;
  mechanical reduction requires vendoring/forking (deferred).
- Add pre-push `ci-check-full` hook that runs `just ci-check`
  (including test-race) before allowing push. CI cannot host the race
  detector reliably; this is the local enforcement point. Hook install
  via `pre-commit install --hook-type pre-commit --hook-type commit-msg
  --hook-type pre-push` (also wired into `justfile:install`). Documented
  in CONTRIBUTING.md § Development Setup + README developer section
  and cross-referenced from GOTCHAS §1.1.
- Add `//go:build integration` tag to cmd/audit_integration_test.go
  (other integration test files already tagged; CI + justfile splits
  were already correct).
- Add `macOS Signing (Quill)` section to RELEASING.md documenting the
  5 required Quill env vars + optional QUILL_LOG_FILE, with
  verification commands (codesign, spctl, quill extract signature).

Todos resolved: #116, #118, #120, #121, #197.

Notes:
- Extensive stale Grype/Snyk claims remain in CONTRIBUTING.md,
  docs/dev-guide/, docs/security/, docs/pipeline-v2-compliance.md,
  docs/development/releasing.md — folded into Phase 3 documentation
  sweep.
- .github/workflows/benchmarks.yml still does ad-hoc
  `go install benchstat@latest`; out of this PR's scope; tracked
  for Phase 2 round 2 CI-workflow follow-ups.

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
unclesp1d3r added a commit that referenced this pull request Apr 19, 2026
…audit, pre-push hook

- Add .github/workflows/security.yml (govulncheck, CodeQL Go analyze,
  Trivy filesystem scan). SARIF uploaded to code scanning. Weekly
  schedule plus on-push and PR.
- Correct SECURITY.md to match reality (drop false Grype/Snyk claims,
  explicitly name govulncheck/CodeQL/Trivy/Scorecard/Dependabot).
- Inventory 9 go.mod pseudo-version dependencies with header block and
  inline rationale per entry. All are upstream-never-tagged;
  mechanical reduction requires vendoring/forking (deferred).
- Add pre-push `ci-check-full` hook that runs `just ci-check`
  (including test-race) before allowing push. CI cannot host the race
  detector reliably; this is the local enforcement point. Hook install
  via `pre-commit install --hook-type pre-commit --hook-type commit-msg
  --hook-type pre-push` (also wired into `justfile:install`). Documented
  in CONTRIBUTING.md § Development Setup + README developer section
  and cross-referenced from GOTCHAS §1.1.
- Add `//go:build integration` tag to cmd/audit_integration_test.go
  (other integration test files already tagged; CI + justfile splits
  were already correct).
- Add `macOS Signing (Quill)` section to RELEASING.md documenting the
  5 required Quill env vars + optional QUILL_LOG_FILE, with
  verification commands (codesign, spctl, quill extract signature).

Todos resolved: #116, #118, #120, #121, #197.

Notes:
- Extensive stale Grype/Snyk claims remain in CONTRIBUTING.md,
  docs/dev-guide/, docs/security/, docs/pipeline-v2-compliance.md,
  docs/development/releasing.md — folded into Phase 3 documentation
  sweep.
- .github/workflows/benchmarks.yml still does ad-hoc
  `go install benchstat@latest`; out of this PR's scope; tracked
  for Phase 2 round 2 CI-workflow follow-ups.

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
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 go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant