Skip to content

ci(deps): bump docker/build-push-action from 7.1.0 to 7.2.0#29

Open
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot/github_actions/docker/build-push-action-7.2.0
Open

ci(deps): bump docker/build-push-action from 7.1.0 to 7.2.0#29
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot/github_actions/docker/build-push-action-7.2.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 22, 2026

Bumps docker/build-push-action from 7.1.0 to 7.2.0.

Release notes

Sourced from docker/build-push-action's releases.

v7.2.0

Full Changelog: docker/build-push-action@v7.1.0...v7.2.0

Commits
  • f9f3042 Merge pull request #1517 from docker/dependabot/npm_and_yarn/docker/actions-t...
  • 812d5fd chore: update generated content
  • b6f6693 chore(deps): Bump @​docker/actions-toolkit from 0.87.0 to 0.90.0
  • c1c626e Merge pull request #1525 from docker/dependabot/npm_and_yarn/actions/core-3.0.1
  • 51bb284 chore: update generated content
  • 5f7884d chore(deps): Bump @​actions/core from 3.0.0 to 3.0.1
  • e01deff Merge pull request #1521 from docker/dependabot/npm_and_yarn/fast-xml-parser-...
  • 3804d49 chore: update generated content
  • 71e8947 chore(deps): Bump fast-xml-parser from 5.5.7 to 5.8.0
  • 4925ad2 Merge pull request #1526 from docker/dependabot/npm_and_yarn/postcss-8.5.10
  • 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 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)

DaveBugg and others added 3 commits May 21, 2026 15:30
Panels (notably Happ JSON bundles) return the same logical server
multiple times — one outbound per SNI/fingerprint variant for
domain-fronting resilience. Observed on s.stun.su returning 1256
outbounds for happ-macos UA across 303 unique (addr,port,uuid)
servers. The pre-1.3.6 delete-and-insert flow created 1256 Node rows;
the 1.3.6 upsert kept them around forever as orphans (their fp is in
seen_fps so not deleted, but only one row per fp is the matched
'existing' so others are never updated either).

Two fixes:

1. Dedup parsed list by fingerprint before the upsert loop — multiple
   SNI variants of the same (protocol, addr, port, uuid, password)
   collapse to one Node row, last-wins on mutable fields.

2. Collapse legacy duplicates from the DB on every refresh. Pick the
   smallest-id row as the survivor (stable choice — minimizes external
   reference breakage) and transparently remap any active_node_id /
   NodeCircle.node_ids reference from a dup to the survivor before
   deleting the dup. User never notices the cleanup.

Tests: 3 new in TestSubscriptionRefreshDedupsParsed covering parsed
dedup, legacy DB dedup, and cross-reference remap (active + circle
both pointing at dups that get collapsed).
Burn-in on a 1256-node Happ-bundle subscription surfaced four
refresh-related regressions: the active node disappeared after every
refresh, NodeCircle members went dangling, the same logical server
accumulated as ~22x legacy duplicates, and a double-click on
'Update Geo' raced two downloads. This release fixes all four
end-to-end.

Highlights:
- Stable-fingerprint upsert preserves Node.id across refreshes
- Per-subscription refresh mutex (409 on concurrent calls)
- NodeCircle.node_ids and active_node_id transparently remap through
  fingerprint dedup + legacy-duplicate collapse
- Geo update: per-call unique tmp path + frontend/backend mutex pair
- Boot-time active_node_id integrity check now actually runs

7 commits since v1.3.5. 23 new backend tests; full suite 608 passed.
Frontend build + tests clean.

Safe to upgrade from any 1.3.x. Next successful refresh after upgrade
auto-collapses any accumulated legacy duplicates.
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 7.1.0 to 7.2.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@bcafcac...f9f3042)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-version: 7.2.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 github_actions Pull requests that update GitHub Actions code labels May 22, 2026
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 github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant