Skip to content

emudhra-incident-response - #855

Merged
general-kroll-4-life merged 1 commit into
mainfrom
bugfix/emudhra-incident-response
Oct 21, 2026
Merged

general-kroll-4-life merged 1 commit into
mainfrom
bugfix/emudhra-incident-response

Conversation

@general-kroll-4-life

@general-kroll-4-life general-kroll-4-life commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Description

  • Fix security incident per public alert.
  • Use go version 1.26.10 due to stackql dependence on golagci-lint.
  • Upgraded golangci-lint to v2.15.0.

Type of change

  • Bug fix (non-breaking change to fix a bug).
  • Feature (non-breaking change to add functionality).
  • Breaking change.
  • Other (eg: documentation change). Please explain.

Issues referenced.

Public communication: We have a problem.

Evidence

  • Existing test appraratus passes in full.

Checklist:

  • A full round of testing has been completed, and there are no test failures as a result of these changes.
  • The changes are covered with functional and/or integration robot testing.
  • The changes work on all supported platforms.
  • Unit tests pass locally, as per the developer guide.
  • Robot tests pass locally, as per the developer guide.
  • Linter passes locally, as per the developer guide.

Variations

N/A.

Tech Debt

No technical debt is introduced in this change.

Summary:

- Fix security incident per [public alert](https://emudhra.we-have-a-problem.com/).
- Use `go` version `1.26.10` due to `stackql` dependence on `golagci-lint`.
- Upgraded `golangci-lint` to `v2.15.0`.
@general-kroll-4-life
general-kroll-4-life merged commit 836d9fc into main Oct 21, 2026
70 checks passed
@general-kroll-4-life
general-kroll-4-life deleted the bugfix/emudhra-incident-response branch October 21, 2026 00:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant