chore(deps): bump goreleaser/goreleaser-action from 6 to 7#2
Merged
janosmiko merged 1 commit intoApr 6, 2026
Merged
Conversation
Bumps [goreleaser/goreleaser-action](https://github.com/goreleaser/goreleaser-action) from 6 to 7. - [Release notes](https://github.com/goreleaser/goreleaser-action/releases) - [Commits](goreleaser/goreleaser-action@v6...v7) --- updated-dependencies: - dependency-name: goreleaser/goreleaser-action dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
dependabot
Bot
deleted the
dependabot/github_actions/goreleaser/goreleaser-action-7
branch
janosmiko
added a commit
that referenced
this pull request
Apr 16, 2026
Three related bugs found in manual testing: 1. Trivy showed in clusters where Trivy Operator wasn't installed 2. Heuristic showed finding stats from previous clusters 3. Security category appeared at the bottom of the middle column instead of just below Dashboards Root cause for #1 and #2: the SecuritySourcesFn closure indirected through **security.Manager and *map[string]bool pointers pointing at fields on NewModel's local m. Bubbletea passes Model by value, so subsequent Update cycles mutated new copies while the pointers stayed frozen on NewModel's original — forever reading the initial cluster's manager, availability map, and cached FindingIndex. Fix: replace the pointer architecture with a package-level securityHookManager + securityHookAvailability pair protected by a sync.RWMutex, explicitly published by refreshSecuritySources (on every cluster switch) and by handleSecurityAvailabilityLoaded (after the probe completes). The setter is idempotent and safe from any goroutine. Also: - refreshSecuritySources now resets securityAvailabilityByName to a fresh empty map and re-wires the Client's security manager reference, so SEC column counts and the action menu gate both see the new cluster's data immediately. - handleSecurityAvailabilityLoaded rebuilds middleItems when at LevelResourceTypes so the newly-arrived availability data populates the Security category entries asynchronously (the initial build runs with an empty availability map because the probe is async). - buildSecuritySourceEntries restores the availability filter — dead entries for unavailable sources were the user-visible symptom of bug #1. For bug #3: prepend the Security category to TopLevelResourceTypes() instead of appending. Update TestClusterGroupIsFirst/Order test expectations accordingly (Cluster is now at index 1, Security at 0).
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps goreleaser/goreleaser-action from 6 to 7.
Release notes
Sourced from goreleaser/goreleaser-action's releases.
... (truncated)
Commits
ec59f47fix: yargs usage752dedefix: gitignore1881ae0ci: update dependabot settingsfdc5e66chore: gitignore provenance.json51b5b35chore(deps): bump semver from 7.7.3 to 7.7.4 in the npm group (#539)4247c53ci(deps): bump docker/setup-buildx-action in the actions group (#538)c169bfdchore(deps): bump@actions/http-clientfrom 3.0.2 to 4.0.0 in the npm group (...902ab4achore(deps): bump the npm group across 1 directory with 4 updates (#536)c59a691chore: gitignore56cc8b2ci: add job to automate dependabot pre-checkin/vendorDependabot 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)