github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[PR #1235] [MERGED] chore(deps): update useblacksmith/build-push-action action to v2 #7400

New Issue
Closed
opened 2026-04-20 17:41:28 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 17:41:28 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1235
Author: @renovate[bot]
Created: 8/4/2025
Status: ✅ Merged
Merged: 9/28/2025
Merged by: @kolaente

Base: main ← Head: renovate/useblacksmith-build-push-action-2.x

📝 Commits (2)

  • 7133407 chore(deps): update useblacksmith/build-push-action action to v2
  • e94203b add changes

📊 Changes

1 file changed (+4 additions, -2 deletions)

View changed files

📝 .github/workflows/release.yml (+4 -2)

📄 Description

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Type Update Change
useblacksmith/build-push-action action major v1 -> v2

Release Notes

useblacksmith/build-push-action (useblacksmith/build-push-action)

v2: - Breaking Change: Requires setup-docker-builder

Compare Source

⚠️ BREAKING CHANGE

This is a major breaking change from v1. The build-push-action now requires the use of useblacksmith/setup-docker-builder@v1 action before it can be used.

What's Changed
  • Removed: All buildkit setup and stickydisk management functionality has been removed from this action
  • Removed: The action no longer handles buildkit lifecycle management (setup/teardown)
  • New Requirement: You MUST use useblacksmith/setup-docker-builder@v1 before using this action
Migration Guide

Before (v1):

- name: Build and push
  uses: useblacksmith/build-push-action@v1
  with:
    push: true
    tags: user/app:latest

After (v2):

- name: Setup Docker Builder
  uses: useblacksmith/setup-docker-builder@v1

- name: Build and push
  uses: useblacksmith/build-push-action@v2
  with:
    push: true
    tags: user/app:latest
Why This Change?

The separation of concerns provides better modularity:

  • setup-docker-builder handles all buildkit and stickydisk management
  • build-push-action focuses solely on Docker builds and metrics reporting
What This Action Now Does
  • Runs Docker builds against the Blacksmith builder (set up by setup-docker-builder)
  • Reports Docker metrics to the Blacksmith control plane
  • All other Docker build functionality remains the same

⚠️ Attempting to use v2 without first running setup-docker-builder will result in build failures.

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/1235 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 8/4/2025 **Status:** ✅ Merged **Merged:** 9/28/2025 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `renovate/useblacksmith-build-push-action-2.x` --- ### 📝 Commits (2) - [`7133407`](https://github.com/go-vikunja/vikunja/commit/71334070b45adb9f111546376194553b81ab6331) chore(deps): update useblacksmith/build-push-action action to v2 - [`e94203b`](https://github.com/go-vikunja/vikunja/commit/e94203b908f7c4713f192283c216960255ffa736) add changes ### 📊 Changes **1 file changed** (+4 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+4 -2) </details> ### 📄 Description Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [useblacksmith/build-push-action](https://redirect.github.com/useblacksmith/build-push-action) | action | major | `v1` -> `v2` | --- ### Release Notes <details> <summary>useblacksmith/build-push-action (useblacksmith/build-push-action)</summary> ### [`v2`](https://redirect.github.com/useblacksmith/build-push-action/releases/tag/v2): - Breaking Change: Requires setup-docker-builder [Compare Source](https://redirect.github.com/useblacksmith/build-push-action/compare/v1...v2) ##### ⚠️ BREAKING CHANGE This is a major breaking change from v1. The build-push-action now requires the use of `useblacksmith/setup-docker-builder@v1` action before it can be used. ##### What's Changed - **Removed**: All buildkit setup and stickydisk management functionality has been removed from this action - **Removed**: The action no longer handles buildkit lifecycle management (setup/teardown) - **New Requirement**: You MUST use `useblacksmith/setup-docker-builder@v1` before using this action ##### Migration Guide **Before (v1):** ```yaml - name: Build and push uses: useblacksmith/build-push-action@v1 with: push: true tags: user/app:latest ``` **After (v2):** ```yaml - name: Setup Docker Builder uses: useblacksmith/setup-docker-builder@v1 - name: Build and push uses: useblacksmith/build-push-action@v2 with: push: true tags: user/app:latest ``` ##### Why This Change? The separation of concerns provides better modularity: - `setup-docker-builder` handles all buildkit and stickydisk management - `build-push-action` focuses solely on Docker builds and metrics reporting ##### What This Action Now Does - Runs Docker builds against the Blacksmith builder (set up by setup-docker-builder) - Reports Docker metrics to the Blacksmith control plane - All other Docker build functionality remains the same **⚠️ Attempting to use v2 without first running setup-docker-builder will result in build failures.** </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/go-vikunja/vikunja). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS41MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuOTcuMTAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyJdfQ==--> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 17:41:28 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#7400
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?