chore(deps): update docker/build-push-action action to v6.19.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	minor	v6.18.0 → v6.19.0

---

Release Notes

docker/build-push-action (docker/build-push-action)

v6.19.0

Compare Source

• Scope default git auth token to github.com by @​crazy-max in #​1451
• Bump brace-expansion from 1.1.11 to 1.1.12 in #​1396
• Bump form-data from 2.5.1 to 2.5.5 in #​1391
• Bump js-yaml from 3.14.1 to 3.14.2 in #​1429
• Bump lodash from 4.17.21 to 4.17.23 in #​1446
• Bump tmp from 0.2.3 to 0.2.4 in #​1398
• Bump undici from 5.28.4 to 5.29.0 in #​1397

Full Changelog: docker/build-push-action@v6.18.0...v6.19.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the Docker build-push-action dependency in the GitHub Actions workflow from version v6.18.0 to v6.19.0. The update modifies the commit SHA reference to point to the latest version while maintaining identical functionality. This is a standard dependency maintenance update that ensures the workflow benefits from the latest improvements, bug fixes, and potential security patches available in the newer version of the action.

Changes

File(s)	Summary
.github/workflows/docker.yml	Updated Docker build-push-action from v6.18.0 to v6.19.0, changing the commit SHA reference from 263435318d21b8e681c14492fe198d362a7d2c83 to ee4ca427a2f43b6a16632044ca514c076267da23.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Workflow as GitHub Actions Workflow
    participant Meta as Metadata Step
    participant BuildAction as Docker Build-Push Action v6.19.0
    participant Registry as Docker Registry

    Note over BuildAction: Version updated from v6.18.0 to v6.19.0
    
    Workflow->>Meta: Execute metadata step
    Meta-->>Workflow: Generate tags
    
    Workflow->>BuildAction: Trigger build (id: build)
    activate BuildAction
    
    BuildAction->>BuildAction: Build Docker image
    
    Note over BuildAction,Registry: push: true enabled
    
    BuildAction->>Registry: Push Docker image with tags
    Note right of Registry: Tags from steps.meta.outputs.tags
    
    Registry-->>BuildAction: Push confirmation
    deactivate BuildAction
    
    BuildAction-->>Workflow: Build complete

Loading

---

🔗 Cross-Repository Impact Analysis

Enable automatic detection of breaking changes across your dependent repositories. → Set up now

Learn more about Cross-Repository Analysis

What It Does

• Automatically identifies repositories that depend on this code
• Analyzes potential breaking changes across your entire codebase
• Provides risk assessment before merging to prevent cross-repo issues

How to Enable

1. Visit Settings → Code Management
2. Configure repository dependencies
3. Future PRs will automatically include cross-repo impact analysis!

Benefits

• 🛡️ Prevent breaking changes across repositories
• 🔍 Catch integration issues before they reach production
• 📊 Better visibility into your multi-repo architecture

---

▶️ ⚡ AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf

Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

• ⚠️ Potential Issue - May require further investigation.
• 🔒 Security Vulnerability - Fix to ensure system safety.
• 💻 Code Improvement - Suggestions to enhance code quality.
• 🔨 Refactor Suggestion - Recommendations for restructuring code.
• ℹ️ Others - General comments and information.

Interact with the Bot:

• Send a message or request using the format:
  @entelligenceai + *your message*

Example: @entelligenceai Can you suggest improvements for this code?

• Help the Bot learn by providing feedback on its responses.
  @entelligenceai + *feedback*

Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

1. config - shows the current config
2. retrigger_review - retriggers the review

More commands to be added soon.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.41%. Comparing base (629a9cb) to head (b77dc20).
⚠️ Report is 36 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #452   +/-   ##
=======================================
  Coverage   92.41%   92.41%           
=======================================
  Files          15       15           
  Lines         725      725           
=======================================
  Hits          670      670           
  Misses         46       46           
  Partials        9        9           

Flag	Coverage Δ
backend	92.41% <ø> (ø)
integration	92.41% <ø> (ø)
unittests	90.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 629a9cb...b77dc20. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Released in v1.2.0