Skip to content

chore(deps): Bump docker/metadata-action from 5 to 6#1

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/metadata-action-6
Open

chore(deps): Bump docker/metadata-action from 5 to 6#1
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/metadata-action-6

Conversation

@dependabot
Copy link
Copy Markdown

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

Bumps docker/metadata-action from 5 to 6.

Release notes

Sourced from docker/metadata-action's releases.

v6.0.0

Full Changelog: docker/metadata-action@v5.10.0...v6.0.0

v5.10.0

Full Changelog: docker/metadata-action@v5.9.0...v5.10.0

v5.9.0

Full Changelog: docker/metadata-action@v5.8.0...v5.9.0

v5.8.0

Full Changelog: docker/metadata-action@v5.7.0...v5.8.0

v5.7.0

Full Changelog: docker/metadata-action@v5.6.1...v5.7.0

... (truncated)

Commits
  • 80c7e94 Merge pull request #613 from docker/dependabot/npm_and_yarn/docker/actions-to...
  • 8e0ddab chore: update generated content
  • a8db14b chore(deps): Bump @​docker/actions-toolkit from 0.79.0 to 0.90.0
  • 63a7371 Merge pull request #617 from docker/dependabot/npm_and_yarn/csv-parse-6.2.0
  • c6916a6 chore: update generated content
  • aca9205 chore(deps): Bump csv-parse from 6.1.0 to 6.2.1
  • 9dcfe60 Merge pull request #629 from docker/dependabot/npm_and_yarn/handlebars-4.7.9
  • 43dea76 chore: update generated content
  • 7a56f5a chore(deps): Bump handlebars from 4.7.8 to 4.7.9
  • e49e0aa Merge pull request #658 from docker/dependabot/npm_and_yarn/brace-expansion-5...
  • 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)

Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5 to 6.
- [Release notes](https://github.com/docker/metadata-action/releases)
- [Commits](docker/metadata-action@v5...v6)

---
updated-dependencies:
- dependency-name: docker/metadata-action
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

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 24, 2026
xuyushun441-sys pushed a commit that referenced this pull request Jun 3, 2026
…-loop

Four user-reported issues with the desktop shell:

1. Orphaned server on quit/restart. `node one.mjs` is only a launcher — it
   spawns `objectstack serve` as a grandchild. kill_current() used
   Child::kill() (SIGKILL), which the launcher can't forward, so the real
   server was orphaned and kept holding the port + SQLite DB. Now the launcher
   runs as a process-group leader and shutdown sends SIGTERM to the whole group
   (graceful, forwarded to the server) with a SIGKILL fallback; taskkill /T on
   Windows. Validated: port listeners drop to 0 after shutdown.

2. "Repeated refresh" on second launch was a consequence of #1 — the orphan
   held standalone.db, so the new server hit a lock conflict, crashed, and the
   supervisor restarted it in a loop, re-navigating the window each time. Fixed
   by #1 (no orphan -> no conflict).

3. Two windows per menu click. A single click is delivered to both the tray's
   on_menu_event and the global app handler, running every action twice (two
   update dialogs, two Finder windows for Open Data/Reveal Logs). Added a short
   dedup window in handle_menu_id.

4. "Check for updates" gave no feedback and could be clicked repeatedly. Added
   CHECKING/INSTALLING atomic guards (concurrent clicks are no-ops), an
   update-checking event ("Checking for updates…"), and real download progress
   via update-progress; splash + injected banner render both.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

0 participants